Channel
- 404
@obd2006
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,306subscribers
-271 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001907050897 |
|---|---|
| Type | Channel |
| Username | @obd2006 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/obd2006 |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 23:54 | 3,306 | -11 |
| 31 Oct 2026, 01:30 | 3,317 | -8 |
| 28 Oct 2026, 04:57 | 3,325 | -11 |
| 25 Oct 2026, 03:27 | 3,336 | -12 |
| 22 Oct 2026, 01:49 | 3,348 | -13 |
| 18 Oct 2026, 17:57 | 3,361 | -14 |
| 15 Oct 2026, 08:09 | 3,375 | -7 |
| 12 Oct 2026, 10:17 | 3,382 | -20 |
| 5 Oct 2026, 23:16 | 3,402 | -36 |
| 28 Sept 2026, 16:38 | 3,438 | -28 |
| 15 Sept 2026, 14:39 | 3,466 | -18 |
| 11 Sept 2026, 19:01 | 3,484 | -15 |
| 8 Sept 2026, 00:43 | 3,499 | no change |
| 6 Sept 2026, 22:39 | 3,499 | -10 |
| 2 Sept 2026, 07:52 | 3,509 | -13 |
| 30 Aug 2026, 07:12 | 3,522 | -18 |
| 27 Aug 2026, 01:55 | 3,540 | -9 |
| 24 Aug 2026, 10:17 | 3,549 | -9 |
| 21 Aug 2026, 02:13 | 3,558 | -8 |
| 18 Aug 2026, 04:22 | 3,566 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@la7unhaa · 24,629
Telegram ranks this channel #1 of 61 here — alongside 60 others — read 14 September 2026
@eee_ze · 117,971
Telegram ranks this channel #66 of 67 here — alongside 66 others — read 14 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“- 404” (@obd2006), 3,306 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/obd2006.
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.