Telegram RegisterThe public register of Telegram
Telegram profile photo for ‘ 🖤 › 𝐄ׄ𝓵𝕝𝖾ִ𝘀tiׄ𝖾𝕤 忌

Channel

‘ 🖤 › 𝐄ׄ𝓵𝕝𝖾ִ𝘀tiׄ𝖾𝕤 忌

@EllestiesFld3

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

209subscribers

+140 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1004313706039
TypeChannel
Username@EllestiesFld3
Description︎ ︎ ︎ ︎ ﹙ 🗝﹚ : 𝚷оׄдпִ𝕦сӄα нα ︎ ︎ ︎ ︎ υׄнфо 𝕠бязִαтеׄльнα 𝐎ᨰׄn𝕖ִ𝐫 : @OsatoLs ,🖤 ۫ ׅ 𝐀𝗇ׄ𝗼𝕟 : @ellts_bot 𝐒𝕥ִα𝗋t 𝟤𝟮.𝟬𝟐.𝟐𝟧 › 𝐇ִαδор ׄотӄ𝕡ִыт : 𝐇оׄ𝕡мα 𝟏𝟬𝟬 +780 ; 780 Marrige : @Hans_Info
CreatedBetween 1 June 2026 and 9 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live7 November 2026
Measurements held9
On Telegramt.me/EllestiesFld3

Topic

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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.

Previous handles

@EllestiesFld3 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@ell3stieSfld3
held 10 August 2026 – 10 August 2026

Growth

692091399 August 2026 — 69 subscribers10 August 2026 — 69 subscribers16 August 2026 — 82 subscribers23 August 2026 — 106 subscribers29 August 2026 — 135 subscribers6 September 2026 — 127 subscribers14 September 2026 — 138 subscribers7 November 2026 — 209 subscribers7 November 2026 — 209 subscribers9 August 20267 November 2026
9 measurements spanning 91 days, net +140. 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 48–230 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Nov 2026, 21:22209no change
7 Nov 2026, 20:47209+71
14 Sept 2026, 18:15138+11
6 Sept 2026, 05:36127-8
29 Aug 2026, 18:57135+29
23 Aug 2026, 13:07106+24
16 Aug 2026, 07:2382+13
10 Aug 2026, 00:3169no change
9 Aug 2026, 07:1769first reading

Engagement

36 posts held, back to 9 August 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 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.42%
avg views ÷ 209 subscribers
Avg views / post
13.4
17 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
17
of 36 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 November 2026
Posts held36 (9 August 2026 – 7 November 2026)
Views total228
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 21:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
23
Videos
11
Links
22

Lifetime counters from Telegram’s own channel header, read 7 November 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
57s
Average length
19s

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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘1100.0%

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 1 of the 36 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 36 most recent posts we hold, published 9 August 2026 to 7 November 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

Telegram’s own ‘edited’ marker: 1 of 17 posts held from the last 30 days (5.88%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

7 Nov 2026, 19:08 UTC14 viewsread 7 November 2026

﹙🖤 河﹚ 𝐑𝗉 𝗧𝗂ׄ𝕞𝖾 ⁄ 𝐁υᩛ : ︎Минхо ‹ ۫✧ 𝐇ִαчׄαло & 𝐊ִонׄец ︎,ׄ .

7 Nov 2026, 19:07 UTC11 viewsread 7 November 2026
Forwarded from @NemurifloodPhoto

︎ ︎︎ ︎ ۫✧ִׄ 𝐍𝐞ׄ𝕞υ𝓻𝗂 🤩 𝗇ִׄ𝕖ᨰ 𝐕𝗂ִ𝕕𝖾𝗼🎀 🤩 • 🤩 • 🤩 • 🤩 • 🤩 • 🤩 ۫ 🤩ִׄ 𝐓𝗂ִ𝕜𝘁ׄ𝕠𝐤 ׄ▭ׅ ︎︎⑊ 𝐁ׄυᩛ Yeonjun

7 Nov 2026, 19:07 UTC9 viewsread 7 November 2026
Forwarded from @NemurifloodPhoto

︎ ︎︎ ︎ ۫✧ִׄ 𝐍𝐞ׄ𝕞υ𝓻𝗂 🤩 𝗇ִׄ𝕖ᨰ 𝐕𝗂ִ𝕕𝖾𝗼🎀 🤩 • 🤩 • 🤩 • 🤩 • 🤩 • 🤩 ۫ 🤩ִׄ 𝐓𝗂ִ𝕜𝘁ׄ𝕠𝐤 ׄ▭ׅ ︎︎⑊ 𝐁ׄυᩛ Theo

7 Nov 2026, 19:06 UTC8 viewsread 7 November 2026
Forwarded from @seika_floodPhoto

⬜ ꣖ 𖥔𝟎𝟐𝟔 ꣓ 💎 𝐍ִᧉ࣪ω 𝐕𝕚d︩︪ᧉ𐐫 💎𓈒 ִ۫  ‌ֺ‌𐑺𓈒 🤩➿🎀➿🎀➿🤩➿🎀➿🎀➿🤩 🥹🍭🤩 𝐈𝐝 :: 𐐫υrઽ || брать с отметкой🤩 🍭 🥹 🤩🍀🤩𝐂𝐫 :: 𝐆ִ𝕚࣪ຣִᧉ࣪𝗹ִ࣪𝗹ᧉ🤩🍀🤩 🤩➿🎀➿🎀➿🤩➿🎀➿🎀➿🤩 🧡𝐎υrs 𝐓ik 𝐓𐐫k ~ 𝐒ꫀi︩︪kᥲ 𝐅l᥆𐐫d🤎 ❤️ 🤩 #seikarp and reactions🤩❤️

7 Nov 2026, 19:06 UTC6 viewsread 7 November 2026
Forwarded from @nrvflood

➖🩸𝗻𝗋𝗏. 𝖯ибят, ходят слухи што Вайджей ⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ хочет обои нам инфо (подкат, заигрываю, намёк, с сексуальными намерениями, чё ещё) ➿➖➿➖➿➖➿➖ ⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ #nrvrp #сзрп ❤️

7 Nov 2026, 19:05 UTC6 viewsread 7 November 2026
Forwarded from @v31lsf1xPhoto

𝗩𝗘𝗜𝗟𝗦𝗙𝗜𝗫 𝗙𝗟𝗢𝗢𝗗 в активном поиске админов ➖➖ ➿➿➿➿➿➿➿➿➿➿➿ 🌟тᨵ трꫀбуꫀтся ⌨ мᨵнтɑжꫀр (1/2)🤩 ᨵбязɑннᨵстu: рɑспuсывɑть стрoчкu, пoмoгɑть дeлɑть их учɑстнuкɑм, монтuровɑть вuдео. админ по нью (0/2)🌸 ᨵбязɑннᨵстu: uскɑть нью, влuвɑть их и пoддержuвɑть ɑктuв. ɑдмuн пᨵ чɑту и ɑктuву (0/2)⭐️ ᨵбязɑннᨵстu: влuвɑть учɑстнuков, поднuмɑть ɑктuв, следuть зɑ чɑтом чтоб не было нɑрушенuй, делɑть ɑктuв посты/бuнго #v31lsrp #сзрп

7 Nov 2026, 19:05 UTC8 viewsread 7 November 2026
Forwarded from @v31lsf1xPhoto

🌟ы в ɑктивнᨵм пᨵискꫀ сᨵюзᨵв ➿➿➿➿➿➿➿➿➿➿➿➿➿ - рɑбᨵтɑꫀм с пɑпкɑми рп/вз - пдп 1:1/2:2/3:3/4:4 - принимɑꫀм с 0+ - прꫀждꫀ чꫀм нɑписɑть oзнɑкᨵмьтꫀсь с прɑвилɑми ➿➿➿➿➿➿➿➿➿➿➿➿➿ 🌟о зɑключꫀнию сᨵюза пишитꫀ @lilmixw #v31lsrp #сзрп

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

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

“‘ 🖤 › 𝐄ׄ𝓵𝕝𝖾ִ𝘀tiׄ𝖾𝕤 忌” (@EllestiesFld3), 209 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/EllestiesFld3.

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.