Telegram RegisterThe public register of Telegram

Channel

elliinskie

@ellinskye

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

85subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003767514842
TypeChannel
Username@ellinskye
CreatedBetween 1 February 2026 and 14 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/ellinskye

Growth

857 August 2026 — 85 subscribers9 August 2026 — 85 subscribers7 August 20269 August 2026
2 measurements spanning 2 days. 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 84–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 16:4885no change
7 Aug 2026, 18:4785first reading

Engagement

18 posts held, back to 14 June 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 pageof 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 6 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
7
Videos
2
Links
6

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
51s
Average length
26s

Measured directly from 2 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

68 reactions across 12 posts, in 13 distinct kinds. The most used accounts for 19.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53529607204661036241319.1%
custom 53528977390656749431217.6%
custom 5352569010858776043913.2%
custom 5352806118823317591811.8%
custom 5411217837257670815710.3%
custom 527648930020721798545.88%
custom 535279734420513345545.88%
custom 523126660600013276834.41%
custom 537734290620812304234.41%
custom 525798790394598601722.94%
custom 523123320833443962111.47%
custom 525796111623495873011.47%
custom 525807759574803016611.47%

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 areTelegram’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 13 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 68reactions 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 14 June 2026 to 6 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

30 Jun 2026, 09:58 UTC191 viewsread 9 August 2026

здравствуйте союзники, скиньте свои каналы в лс

Signed zeyn

29 Jun 2026, 09:54 UTC211 viewsread 9 August 2026

здравствуйте, союзники и взшники. я ухожу с поста админа и передаю все союзы владельцу, все вопросы к нему.

Signed Khamisova.

27 Jun 2026, 23:52 UTC599 views10 reactionsread 9 August 2026
Video

Collaboration @alfrodofml Cr:Darcy

custom 53525690108587760432custom 53528061188233175912custom 54112178372576708152custom 52764893002072179851custom 53527973442051334551custom 53528977390656749431custom 53529607204661036241

Signed T

26 Jun 2026, 12:22 UTC211 views5 reactionsread 9 August 2026
Video

id:?

custom 54112178372576708152custom 53528061188233175911custom 53528977390656749431custom 53529607204661036241

Signed Erdan

24 Jun 2026, 17:25 UTC302 views11 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 52579879039459860172custom 53527973442051334552custom 53529607204661036242custom 52580775957480301661custom 52764893002072179851custom 53525690108587760431custom 53528061188233175911custom 53773429062081230421

Signed Karimova.

22 Jun 2026, 09:44 UTC398 views0 reactionsread 9 August 2026
Sticker

Sticker, posted without a caption

Signed Karimova.

21 Jun 2026, 08:54 UTC462 views1 reactionsread 9 August 2026

союзники, я убрал юз. переходник - @DLINZX

custom 53529607204661036241

Signed Gafurov.

21 Jun 2026, 06:59 UTC461 views13 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 53525690108587760434custom 53528061188233175913custom 53528977390656749433custom 53529607204661036243

Signed Gafurov.

19 Jun 2026, 18:53 UTC462 views1 reactionsread 9 August 2026

союзники, на ежедневные рп брать: • набор союзов. • набор в чат. • набор админов.

custom 53529607204661036241

Signed Gafurova.

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

Citation-graph rank

Citation-graph rank — 416,570 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

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.

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

“elliinskie” (@ellinskye), 85 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ellinskye.

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.