Telegram RegisterThe public register of Telegram
Telegram profile photo for ӨVΣЯDӨƧΣ🥷🏿

Channel

ӨVΣЯDӨƧΣ🥷🏿

@Oveerds

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

279subscribers

+11 since we began measuring on 3 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001900474354
TypeChannel
Username@Oveerds
CreatedBetween 1 March 2023 and 31 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 October 2026
Last confirmed live4 November 2026
Measurements held8
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/Oveerds

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 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

262279270.53 September 2026 — 268 subscribers4 September 2026 — 269 subscribers13 September 2026 — 262 subscribers26 September 2026 — 270 subscribers14 October 2026 — 274 subscribers14 October 2026 — 274 subscribers27 October 2026 — 273 subscribers4 November 2026 — 279 subscribers3 September 20264 November 2026
8 measurements spanning 63 days, net +11. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 259–282 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 19:17279+6
27 Oct 2026, 23:47273-1
14 Oct 2026, 19:30274no change
14 Oct 2026, 12:22274+4
26 Sept 2026, 18:00270+8
13 Sept 2026, 13:41262-7
4 Sept 2026, 21:21269+1
3 Sept 2026, 06:45268first 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.

Haavir
@Haavirr · 32,644
Telegram ranks this channel #2 of 70 here — alongside 69 others — read 3 September 2026
مجید شیردستیان(معنویت، انرژی اسم، چاکرا)
@majidshirdastian · 32,202
Telegram ranks this channel #24 of 61 here — alongside 60 others — read 4 October 2026

This channel appears in 2 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.

“ӨVΣЯDӨƧΣ🥷🏿” (@Oveerds), 279 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/Oveerds.

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.