Varanus niloticus
Varanus niloticus
(Nile Monitor)
Reptiles-Lizards
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

4 results for Varanus niloticus (Nile Monitor)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
2230 Varanus niloticus Predation/Herbivory Observational Field Stomach contents of dead Nile Monitors in Cape Coral, FL, revealed that they consume a range of... 32946
2231 Varanus niloticus Predation/Herbivory Anecdotal Field Anecdotal reports suggest that Nile Monitors in Cape Coral, FL, opportunistically prey on pond... 32946
2232 Varanus niloticus Predation/Herbivory Anecdotal N/A In Africa Nile Monitors are important predators of Crocodylus niloticus (Nile Crocodile) eggs and... 14111
2234 Varanus niloticus Predation/Herbivory Anecdotal N/A Colonial waterbirds and native turtle eggs and hatchlings may be susceptible to predation. 14111

View all impact types for Varanus niloticus
Data Disclaimer: These data are preliminary or provisional and are subject to revision. They are being provided to meet the need for timely best science. The data have not received final approval by the U.S. Geological Survey (USGS) and are provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the data.

Disclaimer:

The data represented on this site vary in accuracy, scale, completeness, extent of coverage and origin. It is the user's responsibility to use these data consistent with their intended purpose and within stated limitations. We highly recommend reviewing metadata files prior to interpreting these data.

Citation information: U.S. Geological Survey. [2025]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [12/6/2025].

Contact us if you are using data from this site for a publication to make sure the data are being used appropriately and for potential co-authorship if warranted.

For general information and questions about the database, contact Wesley Daniel. For problems and technical issues, contact Matthew Neilson.