Channel
Revision records
@rev_records
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,531subscribers
-43 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002235443586 |
|---|---|
| Type | Channel |
| Username | @rev_records |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/rev_records |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 4 Nov 2026, 00:36 | 5,531 | -6 |
| 1 Nov 2026, 10:30 | 5,537 | -2 |
| 29 Oct 2026, 10:17 | 5,539 | +3 |
| 23 Oct 2026, 12:36 | 5,536 | -4 |
| 20 Oct 2026, 04:06 | 5,540 | -3 |
| 17 Oct 2026, 11:28 | 5,543 | -8 |
| 11 Oct 2026, 04:01 | 5,551 | -2 |
| 5 Oct 2026, 08:18 | 5,553 | -15 |
| 26 Sept 2026, 19:15 | 5,568 | -12 |
| 15 Sept 2026, 15:00 | 5,580 | -6 |
| 11 Sept 2026, 14:42 | 5,586 | +11 |
| 7 Sept 2026, 02:19 | 5,575 | -1 |
| 2 Sept 2026, 11:44 | 5,576 | +1 |
| 30 Aug 2026, 21:43 | 5,575 | no change |
| 30 Aug 2026, 08:14 | 5,575 | -1 |
| 26 Aug 2026, 21:32 | 5,576 | +2 |
| 26 Aug 2026, 02:45 | 5,574 | 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.
@FUTUREDOCTORS_196 · 36,230
Telegram ranks this channel #18 of 77 here — alongside 76 others — read 2 September 2026
@FUTUREDOCTORS_194 · 43,969
Telegram ranks this channel #31 of 89 here — alongside 88 others — read 29 August 2026
@dryoussefmohsen · 33,871
Telegram ranks this channel #32 of 86 here — alongside 85 others — read 5 September 2026
@Medical_Data_Channel · 50,030
Telegram ranks this channel #54 of 82 here — alongside 81 others — read 26 August 2026
This channel appears in 4 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Revision records” (@rev_records), 5,531 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/rev_records.
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.