Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐Ÿ๐Ÿ’.๐Ÿ๐ŸŽ.๐ŸŽ๐Ÿ

Channel

๐Ÿ๐Ÿ’.๐Ÿ๐ŸŽ.๐ŸŽ๐Ÿ

@zosha_14

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

243subscribers

+0 since we began measuring on 11 September 2026

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

Register entry

Telegram ID-1001326561814
TypeChannel
Username@zosha_14
DescriptionI ๐˜ข๐˜ฎ ๐˜ค๐˜ถ๐˜ณ๐˜ญ๐˜บ ๐˜จ๐˜ช๐˜ณ๐˜ญ .
CreatedBetween 1 March 2018 and 31 August 2021 โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded11 September 2026
Last confirmed live11 September 2026
Measurements held2
On Telegramt.me/zosha_14

Growth

24311 Sept 2026, 02:47 โ€” 243 subscribers11 Sept 2026, 03:22 โ€” 243 subscribers11 Sept 2026, 02:4711 Sept 2026, 03: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 242โ€“244 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 03:22243no change
11 Sept 2026, 02:47243first reading

Engagement

20 posts held, back to 8 July 2024 โ€” the 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 20 posts for this entry, the most recent from 12 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
โ‰ˆ1,030
Videos
โ‰ˆ265
Links
โ‰ˆ5

Lifetime counters from Telegramโ€™s own channel header, read 11 September 2026 โ€” not the date at the top of this page, which is when the subscriber count was last read. A count marked โ‰ˆ was rounded by Telegram before we ever saw it โ€” t.me prints these counters in full below 1,000 and to three significant figures above, so โ‰ˆ142,000 means somewhere between 141,500 and 142,499.

Reaction mix

15 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
โค1066.7%
๐Ÿ’”213.3%
๐Ÿ™213.3%
๐Ÿ‘16.67%

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 8 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 15 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 8 July 2024 to 12 June 2025, 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

12 Jun 2025, 20:01 UTC211 views1 reactionsread 11 September 2026
Forwarded from @zosha_2

ุญุณุจูŠ ุงู„ู„ู‡ ูˆู†ุนู… ุงู„ูˆูƒูŠู„ ุนู„ู‰ ูƒูู„ ุดุฎุต ุญุฌู‡ ุนู„ูŠู‡ ุจุธู‡ุฑูŠ ุณูˆุงุก ุงุฏุฑูŠ ุงูˆ ู…ุงุฏุฑูŠ ุญุณุจูŠ ุงู„ู„ู‡ ูˆู†ุนู… ุงู„ูˆูƒูŠู„ ุนู„ู‰ ูƒูู„ ุดุฎุต ุงุบุชุงุจู†ูŠ ุงูŠุงู‹ ูƒุงู†โ€ฆ๐Ÿฉตโœจ

๐Ÿ‘1

4 Jun 2025, 23:00 UTC233 viewsread 11 September 2026
Forwarded from @zosha_2

ุงู†ุง ุงู†ุณุงู†ุŒุงุนุทูŠูƒู ูุฑุต ุจูƒู„ ู…ุงููŠู†ูŠ ู„ูุฏุฑุฌู‡ ุฃุฎู„ูŠูƒ ุชู‘ุณุชุญูŠ ู…ู† ูุฑุตูŠ ู…ูู‚ุงุจู„ ู„ูƒู† ุจู…ุฌุฑุฏ ู…ุงุงุนุทูŠู‘ูƒ ุธู‡ุฑูŠ ู…ุณุชุญูŠู„ ุงุฑุฌุน.

11 May 2025, 22:13 UTCโ‰ˆ1,270 viewsread 11 September 2026
Photo

ุงู„ุฐูƒุฑู‰ ุงู„ุณู†ูˆูŠู‡ ุงู„ุซุงู„ุซู‡ ู„ ูˆูุงู‡ ุจุดูŠุฑ...๐Ÿ’” ุงู„ูุงุชุญู‡ ุนู„ู‰ ุฑูˆุญ ุจุดูŠุฑ ู…ุญู…ุฏ ๐Ÿ™

16 Apr 2025, 23:40 UTC254 views2 reactionsread 11 September 2026
Forwarded from @zosha_2

ุดูƒุฑุง ูŠุงุฑุจ๐Ÿฉต

โค2

16 Apr 2025, 23:40 UTC245 views2 reactionsread 11 September 2026
Forwarded from @zosha_2Photo

Photo, posted without a caption

โค2

16 Apr 2025, 23:39 UTC208 viewsread 11 September 2026
Forwarded from @zosha_2

๏ดฟุงู„ุญูŽู…ุฏู ู„ู„ู‡ู ุฑูŽุจู‘ู ุงู„ุนุงู„ูŽู…ููŠู†๏ดพ

18 Mar 2025, 23:18 UTCโ‰ˆ1,180 views4 reactionsread 11 September 2026

ู…ุงุนู†ุฏูŠ ู…ุดูƒู„ุฉ ูˆูŠ ู†ู‡ุงูŠุฉ ุงู„ุนู„ุงู‚ุงุช ูˆุงฺฏุฏุฑ ุงุชู‚ุจู„ู‡ู† ุจฺฏู„ุจ ุฑุงุถูŠ .. ุจุณ ุนู†ุฏูŠ ู…ุดูƒู„ุฉ ูˆูŠ ุงู„ู†ู‡ุงูŠุฉ ุงู„ู„ูŠ ุชุชุฑูƒ ุจุฑูˆุญูŠ "ู„ูŠุด" ุตุบูŠุฑุฉ ุนู†ุฏูŠ ู…ุดูƒู„ุฉ ูˆูŠ ุงู„ู†ู‡ุงูŠุฉ ุงู„ู„ูŠ ุชุฎู„ูŠู†ูŠ ุงฺฏุนุฏ ุงููƒุฑ ูŠุง ุฌุฒุก ฺ†ุงู† ุญู‚ูŠู‚ูŠ ูˆูŠุง ุฌุฒุก ฺ†ุงู† ฺ†ุฐุจุฉ ูˆ ุงู„ู„ูŠ ุชุฎู„ูŠู†ูŠ ุงฺฏูˆู„ ู…ุซู„ ู…ุงฺฏุงู„ ุฒูŠุฏ ุงู„ู‡ุงุฌุฑูŠ : "ุฅุญู†ู‡ ู„ูˆ ู…ุง ู…ู„ุชู‚ูŠู† ุฃุญุณู† ูˆู„ุง ู‡ุงูŠ ุงู„ู†ู‡ุงูŠุฉ

โค4

10 Feb 2025, 10:40 UTC238 views2 reactionsread 11 September 2026
Forwarded from @zosha_2

ูู ุงู„ูˆู‚ุช ุงู„ู…ูู†ุงุณุจ ุณูŠุฃุชูŠ ุงู„ู…ูู†ุงุณุจ ุงู„ุฐูŠ ูŠุชู†ุงุณุจ ู…ุน ูˆุนูŠูƒ ุŒ ู†ุถุฌูƒ ุŒ ู‚ู„ุจูƒ ูˆูŽ ุฃุญู„ุงู…ูƒ ูู ูุชุฑุฉ ุณุชูƒูˆู† ุฌู…ูŠู„ุฉ ุฌุฏุงู‹ ุจุฅุฐู† ุงู„ู„ู‡ .

โค2

7 Feb 2025, 23:06 UTC249 views1 reactionsread 11 September 2026
Forwarded from @zosha_2

ูƒุงู†ุช ุงู„ูƒุงุฑุซุฉ ูƒู„ู‡ุง ููŠ ุงู„ุฅูุฑุงุทุŒ ุงู„ุฅูุฑุงุท ููŠ ุงู„ุฃู…ู„ ููŠ ุงู„ุญุจุŒ ููŠ ุงู„ุชูˆู‚ุนุงุชุŒ ููŠ ุงู„ุฅู†ุชุธุงุฑ ููŠ ูƒู„ ุดูŠุก.

๐Ÿ’”1

1 Dec 2024, 00:02 UTC343 views2 reactionsread 11 September 2026
Forwarded from @zosha_2Photo

Photo, posted without a caption

๐Ÿ™2

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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 11 September 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐Ÿ๐Ÿ’.๐Ÿ๐ŸŽ.๐ŸŽ๐Ÿโ€ (@zosha_14), 243 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/zosha_14.

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.