Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐞𝐥𝐢𝐚𝐬

Channel

𝐞𝐥𝐢𝐚𝐬

@eliashoshimi

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

87subscribers

+4 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003845232616
TypeChannel
Username@eliashoshimi
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/eliashoshimi

Growth

839086.510 August 2026 — 83 subscribers10 August 2026 — 83 subscribers17 August 2026 — 85 subscribers24 August 2026 — 90 subscribers1 September 2026 — 89 subscribers10 September 2026 — 88 subscribers19 September 2026 — 87 subscribers8710 August 202619 September 2026
7 measurements spanning 40 days, net +4. 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 82–91 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 03:1587-1
10 Sept 2026, 02:2188-1
1 Sept 2026, 02:0689-1
24 Aug 2026, 18:4790+5
17 Aug 2026, 19:2385+2
10 Aug 2026, 14:0083no change
10 Aug 2026, 13:4683first reading

Engagement

19 posts held, back to 2 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

63 reactions across 15 posts, in 13 distinct kinds. The most used accounts for 25.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53552041236187235501625.4%
custom 52516992300110542641117.5%
812.7%
custom 5204132810805238070711.1%
custom 520427101855785502569.52%
custom 543832479320193813346.35%
custom 543820536304634752234.76%
custom 543839450911109887923.17%
23.17%
custom 540013582090662171311.59%
custom 543824980307295967211.59%
custom 543849290681184524011.59%
custom 543862139075850557411.59%

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

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

9 Aug 2026, 16:15 UTC27 views4 reactionsread 10 August 2026

навигацию чуууть-чуть поменяю, а пока.. может анон?

4

7 Aug 2026, 10:41 UTC38 views14 reactionsread 10 August 2026
Photo

Happy birthday Elias 🤩

custom 535520412361872355014

6 Aug 2026, 10:45 UTC56 viewsread 10 August 2026

anon: Здравствуйте Элиас, можно вас нарисовать? me: Да, конечно

6 Aug 2026, 10:44 UTC53 viewsread 10 August 2026

anon: Вы самая шикарная me: Спасибо большое💗

6 Aug 2026, 10:13 UTC54 views2 reactionsread 10 August 2026

Возможно выложу сегодня

2

4 Aug 2026, 11:44 UTC65 views2 reactionsread 10 August 2026

anon: Кисуня, поздравляю с 100 подписчиков в тик токе! —Уто(Эмай но не Эмай, да) me: Спасибо большое🐾

custom 52516992300110542642

4 Aug 2026, 11:42 UTC66 views2 reactionsread 10 August 2026

Урааа 100, спасибо большое 🐾

custom 52516992300110542642

4 Aug 2026, 11:42 UTC63 views2 reactionsread 10 August 2026
Photo

…..ухты

custom 52042710185578550252

4 Aug 2026, 11:39 UTC56 views1 reactionsread 10 August 2026

Скоро вот-вот 100 пдп.. добью, и возможно устрою розыгрыш

custom 52042710185578550251

3 Aug 2026, 22:27 UTC60 views14 reactionsread 10 August 2026

Кстати я новые реакции поставила да

custom 52516992300110542647custom 52042710185578550253custom 52041328108052380702custom 54001358209066217131custom 54383247932019381331

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

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 2 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.

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

“𝐞𝐥𝐢𝐚𝐬” (@eliashoshimi), 87 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/eliashoshimi.

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.