Channel
03:03
@Repewiso
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,287subscribers
+14 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001538244222 |
|---|---|
| Type | Channel |
| Username | @Repewiso |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 October 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/Repewiso |
Topic
Music — 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 2 October 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 09:56 | 1,287 | +2 |
| 2 Oct 2026, 04:28 | 1,285 | no change |
| 19 Sept 2026, 00:01 | 1,285 | +3 |
| 15 Sept 2026, 00:18 | 1,282 | +6 |
| 11 Sept 2026, 13:17 | 1,276 | +3 |
| 7 Sept 2026, 04:39 | 1,273 | +2 |
| 30 Aug 2026, 09:39 | 1,271 | +2 |
| 27 Aug 2026, 19:58 | 1,269 | -1 |
| 24 Aug 2026, 17:53 | 1,270 | +2 |
| 21 Aug 2026, 06:44 | 1,268 | -5 |
| 18 Aug 2026, 09:33 | 1,273 | +1 |
| 15 Aug 2026, 14:47 | 1,272 | -1 |
| 14 Aug 2026, 18:45 | 1,273 | 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.
@Minorammusic · 28,504
Telegram ranks this channel #11 of 72 here — alongside 71 others — read 9 September 2026
@falleghahvehh · 19,169
Telegram ranks this channel #33 of 52 here — alongside 51 others — read 3 October 2026
@ub_pdf_katab_ac · 59,513
Telegram ranks this channel #67 of 83 here — alongside 82 others — read 22 August 2026
@ittahass · 109,733
Telegram ranks this channel #68 of 73 here — alongside 72 others — read 14 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“03:03” (@Repewiso), 1,287 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/Repewiso.
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.