One year of sewage bypasses in Tasmania Every bypass event published by TasWater for 2024-25, drawn at its real start time and duration. Textured rows are plants whose bypass record is incomplete or could not be positioned on this timeline. Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun event timing not published in AER Rosebery: bypass count published, event timing not published. Select for the plant record and its source. Rosebery 94 events · 94.7 ML · event dates available only on request Ti Tree Bend: bypass count published, event timing not published. Select for the plant record and its source. Ti Tree Bend 139 events · 343.8 ML · event dates available only on request record published Norwood: 19 published bypass event(s). Select for the plant record, its events and their sources. Norwood 38.9 ML Cameron Bay: 20 published bypass event(s). Select for the plant record, its events and their sources. Cameron Bay 36.0 ML Prospect Vale: 31 published bypass event(s). Select for the plant record, its events and their sources. Prospect Vale 27.6 ML Prince of Wales (POW): 16 published bypass event(s). Select for the plant record, its events and their sources. Prince of Wales (POW) 15.8 ML Geeveston: 9 published bypass event(s). Select for the plant record, its events and their sources. Geeveston 13.1 ML Sheffield: 1 published bypass event(s). Select for the plant record, its events and their sources. Sheffield 10.1 ML Rosny: 3 published bypass event(s). Select for the plant record, its events and their sources. Rosny 8.2 ML Newnham: 14 published bypass event(s). Select for the plant record, its events and their sources. Newnham 7.0 ML Dover: 39 published bypass event(s). Select for the plant record, its events and their sources. Dover 3.3 ML Cambridge: 2 published bypass event(s). Select for the plant record, its events and their sources. Cambridge 0.6 ML Bridgewater (Green Point): 24 published bypass event(s). Select for the plant record, its events and their sources. Bridgewater (Green Point) 0.5 ML Ranelagh: 7 published bypass event(s). Select for the plant record, its events and their sources. Ranelagh 0.2 ML Selfs Point: 8 published bypass event(s). Select for the plant record, its events and their sources. Selfs Point 0.1 ML (+7 vol. unknown) Riverside: 7 published bypass event(s). Select for the plant record, its events and their sources. Riverside 0.0 ML zero bypass events reported 61 plants reporting zero bypass events. Select for what "zero reported" does and does not mean, and for the plants behind this count. reported: zero 61 plants AER states zero events 53 of those 61 plants also recorded at least one treated-effluent compliance statistic below 100%. Select for the definition and the contributing plants. A separate, orthogonal question — effluent-treatment performance, not bypass status: 53 of these 61 plants recorded at least one treated-effluent compliance statistic below 100%. 200 bypass events published with dates. Select for the definition and the plants they were extracted from. 200 events extracted from 77 TasWater Level 2 Annual Environmental Reviews, 2024-25. Bar position and width are the reported start time and duration; brief events are drawn at a 2.4px minimum. Colour intensity is volume. Cyan hatch = event published with no recorded volume. Amber hatch/stipple = bypass reporting incomplete or unresolved for that plant. Bypasses are not the same as effluent non-compliance, and neither covers spills from the sewer network, which is reported separately and not published as events.

Select any plant row, the zero-reported block, or the event count in the footnote to see the records behind it. Tab to move between them, Enter to open, Esc to close.

Provenance

Analytical commit
d0f13822e554ffbecbb6b97305115ce9241b692f
Input source
the working tree at that commit
Analytical inputs
clean — no uncommitted edits to the data this wall was built from
Reporting period
2024-25 (2024-07-01 to 2025-06-30)
View-model schema
wall.json v2
Build manifest
e772cd37be5f674d1fd1b722c96f42f21bea67629400bc18e7640695e14de0f9
aer_2024_25.json
6d9f8569d2916843101840c9ee45ae35ab7fc654d2ba588683449f61922f5e3a
bypass_events.csv
be6337d1045a20156652c0ac119059dc5361d96240410bd0aabce75238ff078a
independent_statistics.json
818a316a6ddf44b7079386900a1e015672fcb60b259dce2ce6514f93aa73e044
parameters.csv
d8e30b3ab071c677cf0cdb12f5b4871b6db9c6d5663a3a6f441326a50e9a7514
plants.csv
34d3e711237bf6632108d7e70599a2392dec63b25a826f4c965116f5d4002f5d

No generation timestamp is recorded: this page is a deterministic function of the inputs above, and a clock reading would weaken that guarantee without telling you anything about the data.