Telegram RegisterThe public register of Telegram
Telegram profile photo for †⃟ᛝ⃝𝐈𝐍𝐅𝐎 هرا༒

Channel

†⃟ᛝ⃝𝐈𝐍𝐅𝐎 هرا༒

@shinshiinf

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

8subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002948588978
TypeChannel
Username@shinshiinf
Created2 December 2025measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 12 September 2026
On Telegramt.me/shinshiinf

Growth

787.511 August 2026 — 8 subscribers12 August 2026 — 8 subscribers26 August 2026 — 7 subscribers4 September 2026 — 8 subscribers11 August 20264 September 2026
4 measurements spanning 24 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 7–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 04:588+1
26 Aug 2026, 18:547-1
12 Aug 2026, 16:178no change
11 Aug 2026, 06:498first reading

Engagement

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

Recent posts

28 Jul 2026, 21:30 UTC104 viewsread 12 August 2026

ⓘS༒SORRY Я LЮБЛЮ Б3З ОТН0ШЕНИЙ. . . ) ) ⓘ

10 Jul 2026, 22:43 UTC334 viewsread 12 August 2026

ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ

10 Jul 2026, 22:42 UTC334 viewsread 12 August 2026
Photo

ᅠᅠᅠᅠᅠᅠᅠ༒ 𝐋𝐀'𝐓𝐑𝐀 ༒ 𝐃𝐈𝐌𝐄𝐍𝐒𝐈𝐎𝐍𝐒. ༒ ᛝ⃝ᛝ†⃟ⓘХ0ЧЕШЬ Б#ТЬ СО МН0Й?!!! ТЫ ДОLЖНА Б#ТЬ ⓘ DUNI SWITCH TAKEN ⓘ ༒𝐂𝐎𝐍𝐅𝐄𝐑𝐄𝐍𝐂𝐄 ༒𝐀𝐍𝐎𝐍༒ 𝐁𝐋𝐎𝐆༒𝐖𝐎𝐑𝐊༒ 𝐈𝐍𝐈𝐓𝐈𝐀𝐋༒𝐂𝐑𝐀𝐒𝐇༒𝐅𝐀𝐍𝐒༒ 𝐏𝐋𝐀𝐘𝐋𝐈𝐒𝐓 не отношусь к рейд/докс деятельности и т.д. знакомлюсь. онли вирт +15.мое отношения к вам зависит от вас. иницы: @b4ff3r @Bluelagoon_kf @FARDFY_FM @Q4R1X @FC1NVELO @edemfmly

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

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

“†⃟ᛝ⃝𝐈𝐍𝐅𝐎 هرا༒” (@shinshiinf), 8 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/shinshiinf.

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.