Telegram RegisterThe public register of Telegram
Telegram profile photo for eblanko. :: life.

Channel

eblanko. :: life.

@eblanko_life

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

14subscribers

+0 since we began measuring on 15 September 2026

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

Register entry

Telegram ID-1003923001199
TypeChannel
Username@eblanko_life
CreatedBetween 1 April 2026 and 18 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 September 2026
Last confirmed live16 September 2026
Measurements held2
On Telegramt.me/eblanko_life

Growth

1415 Sept 2026, 04:47 — 14 subscribers15 Sept 2026, 05:22 — 14 subscribers15 Sept 2026, 04:4715 Sept 2026, 05:22
2 measurements taken within a single day. 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 13–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 05:2214no change
15 Sept 2026, 04:4714first reading

Engagement

20 posts held, back to 18 August 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.

ERR · 30 days
204.5%
avg views ÷ 14 subscribers
Avg views / post
28.6
16 posts measured
Reaction rate
19.9%
reactions ÷ views · ER floor
Posts in window
16
of 20 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. It is computed over the 15 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 September 2026
Posts held20 (18 August 202611 September 2026)
Views total458
Reactions total87
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Sept 2026, 05: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
11
Videos
19
Links
3

Lifetime counters from Telegram’s own channel header, read 15 September 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
1m 36s
Average length
12s

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

101 reactions across 19 posts, in 17 distinct kinds. The most used accounts for 25.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54653426414597148502625.7%
1918.8%
custom 53167447831321409311413.9%
custom 546309791116219637776.93%
custom 543364397892895952665.94%
custom 546525940069855066665.94%
custom 546528121913241562765.94%
custom 528773387248052360143.96%
custom 528771332965194515832.97%
custom 539812301884309407521.98%
❤‍🔥21.98%
custom 539785999075091858810.99%
custom 541594904008697155010.99%
🆒10.99%
🍾10.99%
💘10.99%
🤩10.99%

Custom emoji. 11 of the rows above are 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 19 of the 20 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 101 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 18 August 2026 to 11 September 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

11 Sept 2026, 18:14 UTC9 views5 reactionsread 15 September 2026

😀 #matt — спасибо за старание. нам очень приятно!

custom 52877338724805236012custom 52877133296519451581custom 53981230188430940751custom 54159490400869715501

Signed 𝓼𝓼𝓼𝓻.

11 Sept 2026, 16:49 UTC12 views3 reactionsread 15 September 2026

🌟

custom 52877133296519451581custom 52877338724805236011custom 54653426414597148501

Signed 𝓼𝓼𝓼𝓻.

9 Sept 2026, 11:37 UTC14 views5 reactionsread 15 September 2026

участвуем!🌟

custom 54653426414597148502custom 52877133296519451581custom 52877338724805236011custom 53167447831321409311

Signed 𝓼𝓼𝓼𝓻.

7 Sept 2026, 13:22 UTC20 views5 reactionsread 15 September 2026
Photo

❌❌❌❌𝗲𝗯𝗹𝗮𝗻𝗸𝗼 𝗳𝗹𝗼𝗼𝗱. ❌❌❌❌🍼🤩🗒🗒🗒🤩 ❌🤩🤩𝗡𝗘𝗪 𝗙𝗔𝗠𝗜𝗟𝗬 𝗨𝗡𝗜𝗢𝗡.🤩🤩 🤩егодня был перезаключен дружеский союз на семейный, с проектом «𝗜𝗻𝘁𝗲𝗿𝗹𝘂𝗱𝗲 𝗳𝗹𝗼𝗼𝗱.» теперь они для нас тучка, а мы иннокентий.⭐️ 𝗟𝗜𝗙𝗘. :: @lifebyinterlude 𝗜𝗡𝗙𝗢. :: @interlude_inf 𝗧𝗥𝗔𝗖𝗞𝗘𝗥. :: @himedereee #EBL_union

custom 54653426414597148502custom 53167447831321409311custom 53978599907509185881custom 53981230188430940751

Signed 𝓼𝓼𝓼𝓻.

3 Sept 2026, 04:35 UTC46 views7 reactionsread 15 September 2026
Video

🍼🔤ew video. 🍼 ❌🗒 id. :: trend. ❌❌🗒 creator. :: matt. #EBL_video

custom 54653426414597148503custom 53167447831321409311custom 54336439789289595261custom 54630979111621963771custom 54652594006985506661

Signed 𝓼𝓼𝓼𝓻.

1 Sept 2026, 20:07 UTC31 views8 reactionsread 15 September 2026
Video

🍼🔤ew video. 🍼 ❌🗒 id. :: trend. ❌❌🗒 creator. :: matt. #EBL_video

custom 54652812191324156272custom 54653426414597148502custom 53167447831321409311custom 54336439789289595261custom 54630979111621963771custom 54652594006985506661

Signed 𝓼𝓼𝓼𝓻.

1 Sept 2026, 16:03 UTC22 views4 reactionsread 15 September 2026

🎁

custom 54653426414597148502custom 53167447831321409311custom 54652594006985506661

1 Sept 2026, 15:59 UTC24 views7 reactionsread 15 September 2026
Photo

🔤𝗲𝘄 𝘂𝗻𝗶𝗼𝗻. сегодня был заключен союз с прекрасным проектом, под названием «𝘏𝘐𝘔𝘌𝘙𝘈 𝘍𝘓𝘖𝘖𝘋.» надеемся на долгое сотрудничество. 𝗜𝗡𝗙𝗢. — @himerafloodinfo 𝗟𝗜𝗙𝗘. — @himerafloodlife 𝗧𝗥𝗔𝗖𝗞𝗘𝗥. — @himeraok #EBL_union

custom 53167447831321409312custom 54653426414597148502custom 54630979111621963771custom 54652594006985506661custom 54652812191324156271

31 Aug 2026, 20:43 UTC24 views9 reactionsread 15 September 2026
Video

🍼🔤ew video.🍼 ❌🗒 id. :: trend. ❌❌🗒 creator. :: matt. #EBL_video

custom 54653426414597148503custom 53167447831321409312custom 54630979111621963772custom 54336439789289595261custom 54652812191324156271

30 Aug 2026, 16:21 UTC41 views8 reactionsread 15 September 2026
Video

🍼🔤ew video.🍼 ❌🗒 id. :: trend. ❌❌🗒 creator. :: matt. #EBL_video

custom 54653426414597148503custom 53167447831321409312custom 54336439789289595261custom 54630979111621963771custom 54652594006985506661

26 Aug 2026, 17:49 UTC55 views8 reactionsread 15 September 2026
Video

🍼🔤ew video.🍼 ❌🗒 id. :: our. вроде. ❌❌🗒 creator. :: matt. #EBL_video.

custom 54653426414597148504custom 53167447831321409311custom 54336439789289595261custom 54630979111621963771custom 54652594006985506661

Showing the 12 most recent of 20 posts we hold for @eblanko_life. 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 4 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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“eblanko. :: life.” (@eblanko_life), 14 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/eblanko_life.

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.