Channel
@geysertimes
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
20subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001075577752 |
|---|---|
| Type | Channel |
| Username | @geysertimes |
| Description | Official announcements channel for GeyserTimes.org |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 3 |
| On Telegram | t.me/geysertimes |
Science — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 1 October 2026 and assigned it the closest of 31 fixed categories, at 60% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 07:23 | 20 | no change |
| 4 Sept 2026, 15:39 | 20 | +1 |
| 7 Aug 2026, 21:13 | 19 | first reading |
20 posts held, back to 26 October 2019 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 22 April 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
No internet? No problem. Just in time for Yellowstone park opening we have released new versions of the GeyserTimes for Android and iOS apps. Install now to keep a tab on your favorite geysers on the go. 🌎 #EarthDay
We’ve added UNNG-BBG-13 to our database, the new feature northeast of Outpost in Biscuit Geyser Basin.
We'd like to remind everyone that flags should not be used for incorrect primary/secondary assignments. Instead, contact us via [email protected] so we can manually take care of the problem. A more comprehensive guideline on when to use flags will follow at a later point. Thanks for your understanding and support!
FYI the ability to create accounts has been suspended for the time being until we can create some more robust controls
Due to a recent database update the apps tried to sync too many entries at once. We've remedied the situation and apps should start syncing again. Should that not be the case please let us know. Otherwise we'll consider the incident resolved.
We have had multiple reports of issues syncing the app. We are aware of the problem and are currently investigating the incident. The website seems unaffected and remains operational.
The GeyserTimes for Android 4.1.0 update is full of exiting features! To learn more about these, read our blog post: https://medium.com/geysertimes/geysertimes-for-android-4-1-0-50401f45297c
UNNG-GHG-18, a small geyser located northeast of Marmot Cave and therefore also being called "Marmot's Tail" occasionally, as well as UNNG-GHG-15, a geyser located on the east side of the boardwalk towards Solitary, have been added to GeyserTimes. We greatly appreciate the valuable input we received during this process.
Are you feeling adventurous today? Join the beta and download the latest GeyserTimes for Android release on the Google Play Store to help us test new exiting features! https://play.google.com/store/apps/details?id=org.application.geysertimes
Still looking to get in the mood for Halloween? 🦇 Head on over to https://chat.geysertimes.org for an eery experience. You won't be disappointed. And maybe you'll also catch a geyser or two 😉
We've just given our website a slight facelift with an overhauled navigation bar and footer. We hope you like it 😊 As a 501(c)(3) nonprofit organization we rely on donations. You can help us at no extra cost to you. Simply shop at smile.amazon.com/ch/84-3245322 or with AmazonSmile ON in the Amazon Shopping app and AmazonSmile donates 0.5% of eligible purchases to GeyserTimes. With Prime Day sales on October 13 & 14, …
After a long silence on the photo contest held this spring, here's the full list of the winning geyser photos and photographers. Enjoy the wonderful contest entries on our blog post: https://medium.com/geysertimes/announcing-the-winners-of-the-geysertimes-photo-contest-632df410e140
Showing the 12 most recent of 20 posts we hold for @geysertimes. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 September 2026 — this entry's latest reading, not the date you are reading this.
“GeyserTimes” (@geysertimes), 20 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/geysertimes.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.