Channel
@unionWanders
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004317631293 |
|---|---|
| Type | Channel |
| Username | @unionWanders |
| Created | Between 1 June 2026 and 14 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 3 times, most recently 6 October 2026 |
| On Telegram | t.me/unionWanders |
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 3 October 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 13 Sept 2026, 10:20 | 2 | -1 |
| 5 Sept 2026, 07:36 | 3 | -1 |
| 28 Aug 2026, 01:27 | 4 | -1 |
| 20 Aug 2026, 23:54 | 5 | +1 |
| 14 Aug 2026, 05:18 | 4 | +1 |
| 13 Aug 2026, 14:17 | 3 | no change |
| 6 Aug 2026, 18:18 | 3 | first reading |
8 posts held, back to 14 July 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 8 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
союзы @UMBR44A 1) @Osirisfml 2) @tox1cyeb4ny 3) @SULE1M4N0VS 4) @FK0NIXXAI 5) @Ex1le3 6) @GR2Z4R 7) @CNFS1MS 8) @dragondaay 9) @ZATKHI_CEBY 10) @DUSKWRD 11) @ALTAEVSKY 12) @ka7rma 13) @DAGGERSKIE 14) @SEXTAZY_FM 15) @SAXESFULL 16) @LaTierra_FM 17) @deliverskie 18) @miumiuvskie 19) @hanging_jsm 20) @CIRCUSRSR 21) @Tribunal_of 22) @DEMONS1FML 23) @nekoworld4u 24) @toxicvisuals 25) @GLDBULLS 26) @STARDUSTFML 27) @GDN1ST…
Союзы @me1oge Blade — Velours — Sirene — Silvermis — Alcatraz — Ambassador — Melour — Belüwer — Design Asscorbinka
личные правила @UMBR44A 1. работаю с папками рп/актив/актив+рп/вз. папка рп — приоритет. 2. посты для рп кидаю в лс, от вас прошу того же. 3. пост о заключении по договоренности. 4. чистки НЕ провожу, в них НЕ участвую. 5. выходных нет, отвечаю в любой день в свободное время. 6. все рп держатся 3 часа. 7. проверка подписок допов делается по моему желанию. ботов активирую, шаблоны заполняю. 8. нормы у папки актив нет…
личные правила @me1oge 1. каждый репост держу 3 часа. 2. посты на рп прошу скидывать в лс. 3. папки рп/вз. 4. я могу отказаться от союза, не говоря причины. 5. рп после 20:00 не делаю. 6. пост о заключении с того, кто предложил союз. 7. чистки не делаю,не участвую.
Sticker, posted without a caption
Правила заключения союза с конференцией «WANDERS». @wandersssmj 1. Работаем с папками: Рп/Вз/Актив/Актив+рп (смотрите личные правила следящих) Подписка: 1:1 до 12:12 (пока что!!) О разрыве, смене юза — писать следящему. Допам дается 2-3 дня на подписку. Потом разрыв. Если имеются какие то непредвиденные обстоятельства — оповещать следящего 2. Формат союзов. Заключаем союзы с каналами от 50+ подписчико…
Messages in this channel will no longer be automatically deleted
Messages in this channel will be automatically deleted after 1 day
Showing the 8 most recent of 8 posts we hold for @unionWanders. 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.
Named by 2 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Wanders union” (@unionWanders), 2 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/unionWanders.
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.