Channel
@OrdenPark
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
353subscribers
+18 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001978597954 |
|---|---|
| Type | Channel |
| Username | @OrdenPark |
| 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 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/OrdenPark |
Giveaways & airdrops — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 05:57 | 353 | +2 |
| 7 Sept 2026, 08:00 | 351 | +7 |
| 29 Aug 2026, 22:58 | 344 | +4 |
| 21 Aug 2026, 23:49 | 340 | +1 |
| 15 Aug 2026, 15:22 | 339 | +4 |
| 8 Aug 2026, 07:04 | 335 | no change |
| 7 Aug 2026, 13:30 | 335 | first reading |
6 posts held, back to 7 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
23 КУШ Июль 26 Подай заявку! Для участия в розыгрыше необходимо прислать в комментарии к посту расположенному в группе Ордена в ТГ https://t.me/OrdenPark или в ВК https://vk.ru/club237258174 1) Скриншот из таксометра за Июль 2) Фамилию И.О. В Июле: -25.000₽ грязью - 1 билет; -Сумму КУШа узнаем на стриме; -Розыгрыш в прямом эфире (Ютуб и ВК) 09.08.26 Начало стрима 21:00 Участвовать могут все водители парка Орден,…
22 КУШ Июнь 26 Победитель номер 32 Смирнов РГ Поздравляем! 30.450₽ уже на балансе таксометра
22 КУШ Июнь 26 Победителя выявим с помощью Random.org в прямом эфире на канале Женя Такси Старт 05.07.2026 в 21:00 ——————- Вступи в Орден, и начни зарабатывать вместе со мной! Ссылка, нах: https://t.me/OrdenHelp
22 КУШ Июнь 26 Подай заявку! Для участия в розыгрыше необходимо прислать в комментарии к посту расположенному в группе Ордена в ТГ https://t.me/OrdenPark или в ВК https://vk.ru/club237258174 1) Скриншот из таксометра за Июнь 2) Фамилию И.О. В Июне: -25.000₽ грязью - 1 билет; -Сумму КУШа узнаем на стриме; -Розыгрыш в прямом эфире (Ютуб и ВК) 05.07.26 Начало стрима 21:00 Участвовать могут все водители парка Орден,…
21 КУШ Май 26 Победитель Выиграл Номер 218 Исаев СА Поздравляем 🥳 30.450₽ закинули на баланс таксометра 😘
21 КУШ Май 26 Победителя выявим с помощью Random.org в прямом эфире на канале Женя Такси Старт 07.06.2026 в 21:00 ——————- Вступи в Орден, и начни зарабатывать вместе со мной! Ссылка, нах: https://t.me/OrdenHelp
Showing the 6 most recent of 6 posts we hold for @OrdenPark. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Орден” (@OrdenPark), 353 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/OrdenPark.
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.