Current level recorded at
5:00pm, Wednesday 25th May BST
(4:00pm, Wednesday 25th May GMT)
Change from previous measurement: -0.080m
(recorded at 4:45pm, Wednesday 25th May BST)
Important! The levels for this location are measured relative to sea level, not relative to the riverbed. The levels shown here do not, therefore, necessarily represent the actual depth of the water.
This is a tidal level, measured from mean sea level rather than from the river bed. It can, therefore, be negative, and does not give any indication of water depth. Tidal levels are not necessarily updated frequently, and may not reflect tidal movements throughout the day.
The usual range of the Tide at Cromer is between -2.25m and 2.67m. It has been between these levels for 90% of the time since monitoring began.
The typical recent level of the Tide at Cromer over the past 12 months has been between -2.75m and 3.05m. It has been between these levels for at least 150 days in the past year.
The highest level ever recorded at the Tide at Cromer is 3.76m, reached on Thursday 5th December 2013 at 8:00pm.
Note that this data may not take account of recent measurements, as we wait until a level has been verified by the Environment Agency before adding it to our records.
Long term graphs will work better if you rotate your fondleslab into landscape mode.
Darker blue shaded areas on long term data indicate maximum and minimum levels for the date (you may need to zoom in closer to see them).
Long term data may have gaps where the API data was not available.Download long term data as csv
Note: CSV data will include any outlying values that have been ignored by our graphing system as probably erroneous (eg, because they are ridiculously high compared to the values either side of them). It is your responsibility to filter these out if necessary.
Important! If you are planning to retrieve the csv data automatically, you must read and understand the limitations on the data and its availability.
Do you have local knowledge of this location? If so, please share it here.comments powered by Disqus