Channel
Series IURD
@seriesiurd
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,178subscribers
-94 since we began measuring on 13 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001882023001 |
|---|---|
| Type | Channel |
| Username | @seriesiurd |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 2 times, most recently 30 October 2026 |
| On Telegram | t.me/seriesiurd |
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 28 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 |
|---|---|---|
| 27 Oct 2026, 14:37 | 5,178 | -11 |
| 24 Oct 2026, 11:55 | 5,189 | -6 |
| 21 Oct 2026, 21:51 | 5,195 | -4 |
| 18 Oct 2026, 23:07 | 5,199 | -12 |
| 15 Oct 2026, 23:26 | 5,211 | -6 |
| 12 Oct 2026, 13:08 | 5,217 | -4 |
| 5 Oct 2026, 19:58 | 5,221 | -18 |
| 28 Sept 2026, 11:00 | 5,239 | -29 |
| 15 Sept 2026, 09:58 | 5,268 | -4 |
| 13 Sept 2026, 20:45 | 5,272 | no change |
| 13 Sept 2026, 18:47 | 5,272 | 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.
@ObispoEdirMacedoOficial · 19,362
Telegram ranks this channel #24 of 94 here — alongside 93 others — read 2 October 2026
@renatocardosooficial · 45,615
Telegram ranks this channel #39 of 96 here — alongside 95 others — read 13 September 2026
@oTemplodeSalomao · 20,392
Telegram ranks this channel #47 of 91 here — alongside 90 others — read 27 September 2026
@cancoesIURD · 22,292
Telegram ranks this channel #47 of 94 here — alongside 93 others — read 23 September 2026
@FJU_Brasil · 42,936
Telegram ranks this channel #61 of 98 here — alongside 97 others — read 13 September 2026
@BispoMacedoOficial · 155,672
Telegram ranks this channel #71 of 94 here — alongside 93 others — read 13 September 2026
@IgrejaUniversalOficial · 59,221
Telegram ranks this channel #91 of 96 here — alongside 95 others — read 13 September 2026
This channel appears in 7 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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“Series IURD” (@seriesiurd), 5,178 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/seriesiurd.
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.