Telegram RegisterThe public register of Telegram
Telegram profile photo for корвус на проводе.

Channel

корвус на проводе.

@corvusonawire

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

79subscribers

+2 since we began measuring on 29 August 2026

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

Register entry

Telegram ID-1002621311023
TypeChannel
Username@corvusonawire
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live16 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/corvusonawire

Growth

77797829 August 2026 — 77 subscribers30 August 2026 — 77 subscribers16 September 2026 — 79 subscribers29 August 202616 September 2026
3 measurements spanning 17 days, net +2. 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 77–79 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 01:5979+2
30 Aug 2026, 13:1677no change
29 Aug 2026, 19:0177first reading

Engagement

18 posts held, back to 30 May 2026the 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 18 posts for this entry, the most recent from 2 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 27s
Average length
37s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

74 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 68.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53435404183719300855168.9%
custom 53665976238829873691317.6%
custom 53800741618109809021013.5%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 16 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 74 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 30 May 2026 to 2 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

2 Jul 2026, 14:06 UTC231 views12 reactionsread 29 August 2026
Photo

🤍 #corvusonawire_model #corvusonawire_wip 🤍 расслабляюсь делая модельки для себя. вот такой мальчик зайчик на один сервер. 🥺

custom 53435404183719300858custom 53800741618109809024

30 Jun 2026, 17:42 UTC222 views3 reactionsread 29 August 2026

🤍 #corvusonawire_announcement 🤍 думаю, что пока что закрою заказы, работёнка тяжеловато идёт. как очухаюсь, так сразу откроюсь :) заказы на СКИНЫ принимаю всегда :3

custom 53665976238829873693

23 Jun 2026, 22:08 UTC264 views13 reactionsread 29 August 2026
Photo

🤍 #corvusonawire_model 🤍 ночной вкид.

custom 53435404183719300858custom 53665976238829873695

19 Jun 2026, 12:05 UTC278 views4 reactionsread 29 August 2026
Video

🤍 #corvusonawire_model ; #corvusonawire_comission 🤍 первая часть заказа с прекрасным крылатым мальчиком. ✨заказчик : @voidliminality

custom 53435404183719300854

17 Jun 2026, 13:11 UTC235 views4 reactionsread 29 August 2026
Photo

🤍 #corvusonawire_model 🤍 однажды я точно-точно сделаю всем готовым моделькам визиточки...

custom 53435404183719300854

15 Jun 2026, 20:29 UTC227 views2 reactionsread 29 August 2026
Photo

🤍 #corvusonawire_model ; #corvusonawire_WIP 🤍 пушистик.

custom 53435404183719300852

14 Jun 2026, 20:25 UTC197 viewsread 29 August 2026

🤍 #corvusonawire_shitpost 🤍 Я ТОЛЬКО СЕЙЧАС ПОНЯЛ. у меня был старый юз в посте с заказами…

14 Jun 2026, 14:14 UTC202 views8 reactionsread 29 August 2026
Photo

🤍 #corvusonawire_comission ; #corvusonawire_model 🤍 и бро, которому я пока не сделал видео-визиточку. солнечный?...

custom 53435404183719300855custom 53800741618109809022custom 53665976238829873691

14 Jun 2026, 14:12 UTC175 views4 reactionsread 29 August 2026
Photo

🤍 #corvusonawire_work ; #corvusonawire_model🤍 всякие спойлерочки.

custom 53435404183719300852custom 53665976238829873691custom 53800741618109809021

8 Jun 2026, 21:21 UTC217 views4 reactionsread 29 August 2026

🤍 #corvusonawire_shitpost 🤍 вас когда 56 стало… 🙂 тем не менее спасибо вам за то, что вы со мной!!! я сейчас активно работаю, но все над чем я работаю я не могу вам показать :( так что терпим терпим. скоро один заказ сделаю, вот его я вам покажу <.3

custom 53665976238829873692custom 53435404183719300851custom 53800741618109809021

4 Jun 2026, 20:02 UTC262 views4 reactionsread 29 August 2026
Photo

🤍 #corvusonawire_model ; #corvusonawire_work ; #corvusonawire_WIP 🤍 курение вредит вашему здоровью.

custom 53435404183719300852custom 53665976238829873691custom 53800741618109809021

4 Jun 2026, 10:04 UTC248 views2 reactionsread 29 August 2026
Video

🤍 #corvusonawire_model ; #corvusonawire_comission 🤍 пока я не узнаю новое приложение для монтажа, придётся терпеть капкут… видос слегка сумбурный но ладно. ✨заказчик : @meowzya

custom 53435404183719300852

Showing the 12 most recent of 18 posts we hold for @corvusonawire. 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.

Mentions

Named by 3 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.

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.

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“корвус на проводе.” (@corvusonawire), 79 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/corvusonawire.

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.