Channel
BURMESE Rare Leaks
@notsafeforwork69
On this record: Topic · Growth · Engagement · Cite this entry
1,232subscribers
-57 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001228601584 |
|---|---|
| Type | Channel |
| Username | @notsafeforwork69 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 October 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/notsafeforwork69 |
Topic
Other / unclassifiable — 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 3 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 20:37 | 1,232 | -2 |
| 4 Oct 2026, 17:18 | 1,234 | -9 |
| 3 Oct 2026, 04:10 | 1,243 | no change |
| 24 Sept 2026, 22:57 | 1,243 | -5 |
| 17 Sept 2026, 00:21 | 1,248 | -2 |
| 12 Sept 2026, 20:02 | 1,250 | -4 |
| 9 Sept 2026, 02:37 | 1,254 | -4 |
| 3 Sept 2026, 15:01 | 1,258 | -4 |
| 31 Aug 2026, 02:48 | 1,262 | -5 |
| 28 Aug 2026, 02:34 | 1,267 | -4 |
| 25 Aug 2026, 01:08 | 1,271 | -4 |
| 21 Aug 2026, 10:23 | 1,275 | -3 |
| 18 Aug 2026, 15:28 | 1,278 | -6 |
| 15 Aug 2026, 08:54 | 1,284 | -3 |
| 11 Aug 2026, 13:46 | 1,287 | -3 |
| 8 Aug 2026, 05:36 | 1,290 | +1 |
| 7 Aug 2026, 08:59 | 1,289 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Cite this entry
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“BURMESE Rare Leaks” (@notsafeforwork69), 1,232 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/notsafeforwork69.
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.