Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐“ผ๐“ฝ๐“ฒ๐“ฌ๐“ด๐“ฎ๐“ป ๐“น๐“ช๐“ฌ๐“ด ะ˜ัะผะพะธะปะพะฒโ€™ั

Channel

๐“ผ๐“ฝ๐“ฒ๐“ฌ๐“ด๐“ฎ๐“ป ๐“น๐“ช๐“ฌ๐“ด ะ˜ัะผะพะธะปะพะฒโ€™ั

@stickerpackismoilovs

On this record: Growth ยท Engagement ยท Posts ยท Citations ยท Cite this entry

21subscribers

+10 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003933359915
TypeChannel
Username@stickerpackismoilovs
Created31 July 2026 โ€” measured โ€” dated from the channelโ€™s first post
First recorded14 September 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/stickerpackismoilovs

Growth

1121168 August 2026 โ€” 11 subscribers16 August 2026 โ€” 12 subscribers23 August 2026 โ€” 14 subscribers31 August 2026 โ€” 12 subscribers14 September 2026 โ€” 12 subscribers19 September 2026 โ€” 21 subscribers8 August 202619 September 2026
6 measurements spanning 42 days, net +10. 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 10โ€“23 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 13:3621+9
14 Sept 2026, 02:2312no change
31 Aug 2026, 02:4712-2
23 Aug 2026, 12:0514+2
16 Aug 2026, 08:1812+1
8 Aug 2026, 18:4911first reading

Engagement

14 posts held, back to 31 July 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 1 page of Telegramโ€™s post history, 20 posts per page.

ERR ยท 30 days
142.9%
avg views รท 21 subscribers
Avg views / post
30.0
3 posts measured
Reaction rate
โ€”
this channel exposes no reaction counts
Posts in window
3
of 14 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 11 September 2026
Posts held14 (31 July 2026 โ€“ 11 September 2026)
Views total90
Reactions totalโ€”
Forwards / commentsnot exposed by the public surface โ€” not measured, not estimated
Readings taken14 Sept 2026, 02:23 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.

Recent posts

11 Sept 2026, 12:46 UTC12 viewsread 14 September 2026

ั…ะฐัะฑะธะบ: ๐Ÿ˜ณ๐ŸŒŸ๐ŸŒŸ๐Ÿฅ—๐ŸŒŸ๐ŸŒŸ๐Ÿ˜Š๐Ÿš“๐Ÿ—ก๏ธ๐Ÿ˜โ˜บ๏ธ๐Ÿ‘‹๐Ÿต๐Ÿ‘‹๐Ÿ˜Š๐Ÿ’ฆ๐Ÿ˜›๐Ÿ‘ฎโ€โ™‚๏ธ๐Ÿ’ช๐Ÿคทโ€โ™‚๏ธ

10 Sept 2026, 18:47 UTC23 viewsread 14 September 2026

ะฐะบะฒะฐั€ะตะปัŒะฝะฐั ะพัะตะฝัŒ: ๐Ÿ’™๐Ÿ’š๐Ÿ’›โค๏ธ๐Ÿ๐Ÿ๐Ÿƒ๐Ÿ‚๐Ÿ’๐Ÿ–ผ๏ธ๐ŸŒบ๐Ÿ’๐Ÿ๐Ÿ๐ŸŽ๐Ÿ๐ŸŒฐ๐ŸŒฐ๐Ÿ๐ŸŒฒ

29 Aug 2026, 04:23 UTC55 viewsread 14 September 2026

moon: ๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐ŸŒ™๐Ÿ’ง๐ŸŒ™๐ŸŒ™

23 Aug 2026, 16:35 UTC72 viewsread 14 September 2026

ัั‚ะธะบะตั€ะฟะฐะบะธะผะฝะธ ะพะณะฐะฝะณะฐ ัั€ะฐัˆะฐ ะบะฐะฝะฐะปะธะผะณะฐ ะบะพัˆะปะธะฑ ะบะพะนะธะปะฐะดะฐ

7 Aug 2026, 09:40 UTC178 viewsread 14 September 2026

purple: ๐Ÿคฉ๐Ÿ’œ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐Ÿ˜˜๐Ÿ’‹๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ

4 Aug 2026, 12:38 UTC195 viewsread 14 September 2026

eyes: ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ

1 Aug 2026, 14:02 UTC420 viewsread 14 September 2026

ะั„ั‚ ะณะธั„ั‚ะปะฐั€ ะฒะฐ ัั‚ะฐั€ัะปะฐั€ ะพะปะธะฑ ะผัƒั€ะพะถะฐั‚ ัƒั‡ัƒะฝ ะณะปะฒ: @forismoilov ๐Ÿ’™ ะผัƒะทั‹ะบะฐ: @pesniismoilov๐Ÿฆ‹

31 Jul 2026, 11:37 UTC214 viewsread 14 September 2026

black: ๐Ÿ–ค๐Ÿ’‹๐Ÿ”ซ๐Ÿ’ธ๐Ÿคฉ๐Ÿซฅ๐Ÿซฅ๐Ÿ–โœ…๐ŸŒŸ๐Ÿ’ญโค๏ธโค๏ธ๐Ÿ–ค๐ŸŒŸ๐Ÿฆ‚๐ŸŽ€๐ŸŒŸ๐Ÿงข๐Ÿ˜จ๐Ÿ–ค๐ŸŽ€๐ŸŽ€๐ŸŽ€๐Ÿค๐Ÿ–ค๐Ÿคโค๏ธโ€๐Ÿฉน๐ŸŽ€๐ŸŒŸ๐ŸŒŸ๐ŸŒŸโ™ ๏ธ๐Ÿ–คโœ…โœ”๏ธ๐Ÿช™

31 Jul 2026, 09:56 UTC217 viewsread 14 September 2026

pink: ๐ŸŽ€๐Ÿฉท๐Ÿ’˜๐Ÿ’—๐Ÿ’ž๐Ÿฉท๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ๐Ÿ˜˜๐Ÿซ€๐Ÿ”…๐Ÿ”…๐ŸŒธ๐Ÿ”…๐Ÿ’—๐Ÿ’–โค๏ธ๐ŸŒ•โค๏ธ๐Ÿฉทโค๏ธ๐Ÿคฉโค๏ธโค๏ธ๐Ÿ’—๐ŸŽ€โค๏ธ๐Ÿคฉโค๏ธ๐Ÿฉท๐Ÿคฉ๐Ÿคฉ๐ŸŽ€๐Ÿ’‹๐Ÿคฉ๐Ÿฉท

31 Jul 2026, 09:13 UTC209 viewsread 14 September 2026

red: โค๏ธ๐ŸŽ€โค๏ธ๐Ÿ’‹๐Ÿคฉโค๏ธ๐Ÿ‘„โค๏ธ๐ŸŒ•๐Ÿ’”๐Ÿ’โ™ฅ๏ธ๐Ÿ’‹๐ŸŒŸ๐ŸŒŸ๐Ÿ’‹โค๏ธ๐Ÿฅฐ๐Ÿ’‹๐Ÿ’‹๐Ÿซ€โค๏ธ๐Ÿ’”๐Ÿ’”๐Ÿ’‹๐Ÿฉธ๐Ÿ’•๐Ÿซ‚โค๏ธ

31 Jul 2026, 08:53 UTC200 viewsread 14 September 2026

blue: ๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต๐Ÿฉต

31 Jul 2026, 08:52 UTC192 viewsread 14 September 2026

marine blue: ๐Ÿ‘€๐ŸŒŸ๐Ÿ•Š๏ธ๐Ÿ’™๐Ÿฆ‹๐Ÿ•Š๏ธ๐Ÿ•Š๏ธ๐Ÿคฉ๐Ÿคฉ๐Ÿคฉ๐ŸŒŸ๐Ÿ’™๐Ÿงšโ€โ™‚๐Ÿ•Š๏ธ๐Ÿ•Š๏ธ๐Ÿ•Š๏ธ๐Ÿ•Š๏ธ๐Ÿ•Š๏ธ๐Ÿ‘•๐Ÿ‘•๐Ÿ‘•๐Ÿ‘•๐Ÿ‘•โค๏ธ๐Ÿ’๐ŸŒ‘๐Ÿคฉ๐Ÿคฉ๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ๐ŸŒŸ

Showing the 12 most recent of 14 posts we hold for @stickerpackismoilovs. 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 19 September 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐“ผ๐“ฝ๐“ฒ๐“ฌ๐“ด๐“ฎ๐“ป ๐“น๐“ช๐“ฌ๐“ด ะ˜ัะผะพะธะปะพะฒโ€™ัโ€ (@stickerpackismoilovs), 21 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/stickerpackismoilovs.

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.