Telegram RegisterThe public register of Telegram
Telegram profile photo for Nastasyakoba

Channel

Nastasyakoba

@laprosco

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

49,101subscribers

-260 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002308860970
TypeChannel
Username@laprosco
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 October 2026
Measurements held42
Confirmed unchanged1 time, most recently 19 October 2026
On Telegramt.me/laprosco

Topic

Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 67% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

47,51049,36148,435.57 August 2026 — 49,361 subscribers7 August 2026 — 49,356 subscribers8 August 2026 — 49,352 subscribers9 August 2026 — 49,293 subscribers10 August 2026 — 49,231 subscribers11 August 2026 — 49,178 subscribers12 August 2026 — 49,134 subscribers14 August 2026 — 49,074 subscribers15 August 2026 — 49,068 subscribers17 August 2026 — 48,841 subscribers18 August 2026 — 48,745 subscribers19 August 2026 — 48,606 subscribers20 August 2026 — 48,440 subscribers21 August 2026 — 48,316 subscribers22 August 2026 — 48,165 subscribers24 August 2026 — 48,071 subscribers25 August 2026 — 48,018 subscribers26 August 2026 — 47,924 subscribers27 August 2026 — 47,826 subscribers28 August 2026 — 47,724 subscribers29 August 2026 — 47,681 subscribers30 August 2026 — 47,678 subscribers31 August 2026 — 47,668 subscribers1 September 2026 — 47,687 subscribers2 September 2026 — 47,668 subscribers3 September 2026 — 47,596 subscribers5 September 2026 — 47,659 subscribers8 September 2026 — 47,783 subscribers11 September 2026 — 47,688 subscribers13 September 2026 — 47,651 subscribers14 September 2026 — 47,573 subscribers16 September 2026 — 47,544 subscribers18 September 2026 — 47,510 subscribers2 October 2026 — 47,619 subscribers6 October 2026 — 48,482 subscribers11 October 2026 — 48,817 subscribers14 October 2026 — 49,026 subscribers15 October 2026 — 49,056 subscribers16 October 2026 — 49,049 subscribers17 October 2026 — 49,068 subscribers18 October 2026 — 49,083 subscribers19 October 2026 — 49,101 subscribers49,1017 August 202619 October 2026
42 measurements spanning 73 days, net -260. 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 47,232–49,639 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
19 Oct 2026, 10:0049,101+18
18 Oct 2026, 07:1949,083+15
17 Oct 2026, 09:0549,068+19
16 Oct 2026, 06:3449,049-7
15 Oct 2026, 03:1849,056+30
14 Oct 2026, 01:5949,026+209
11 Oct 2026, 12:2048,817+335
6 Oct 2026, 23:5648,482+863
2 Oct 2026, 00:1747,619+109
18 Sept 2026, 15:4247,510-34
16 Sept 2026, 08:5647,544-29
14 Sept 2026, 15:4147,573-78
13 Sept 2026, 03:5547,651-37
11 Sept 2026, 06:5847,688-95
8 Sept 2026, 13:1847,783+124
5 Sept 2026, 07:1647,659+63
3 Sept 2026, 13:5847,596-72
2 Sept 2026, 04:0347,668-19
1 Sept 2026, 02:0547,687+19
31 Aug 2026, 03:1347,668first reading

Engagement

299 posts held, back to 5 August 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 148 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
20.8%
avg views ÷ 49,101 subscribers
Avg views / post
10,200
92 posts measured
Reaction rate
2.01%
reactions ÷ views · ER floor
Posts in window
93
of 299 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 19 October 2026
Posts held299 (5 August 2026 – 19 October 2026)
Views total941,759
Reactions total18,895
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Oct 2026, 08:09 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

Video runtime
2h 48m
Average length
49s

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

57,519 reactions across 298 posts, in 51 distinct kinds. The most used accounts for 54.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤31,04554.0%
❤‍🔥10,34718.0%
🤩2,0973.65%
😍2,0143.50%
👍1,5352.67%
custom 52805699744049666391,4112.45%
😢1,0081.75%
💘9471.65%
😴5580.97%
😭5410.941%
🙊5120.89%
💯5100.887%
🤣4980.866%
💔4670.812%
🎉4050.704%
💋3820.664%
😎3350.582%
custom 52558617963502240633310.575%
🙏3310.575%
💅2670.464%
31 further kinds1,9783.44%

Custom emoji. 2 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 298 of the 299 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 57,519 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 299 most recent posts we hold, published 5 August 2026 to 19 October 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.

Telegram Stars

Stars received
58
across the posts below
Posts paid on
36
of 298 we hold a reading for · 12%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @laprosco. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 299 most recent posts we hold for this entry, published 5 August 2026 to 19 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
1.00%
3 of 299 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
8,070
over 3 measured posts
Median views · rest
9,850
over 295 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2SDnjbotkT5113 August 202613 August 2026
2VfnxwYEeXD124 August 202624 August 2026
2Vtzqxaravf113 August 202613 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 299 most recent posts we hold, published 5 August 2026 to 19 October 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

18 Oct 2026, 13:00 UTC≈6,530 views137 reactionsread 19 October 2026
Photo

Подборка одежды из предыдущего видео! Куртка кожаная Топ Пиджак Босоножки Брюки магазин Lime ❤️ - очень нравится! 💯 - интересно) 🍓 - совсем не мое

❤107❤‍🔥12🤩7🍓6💘3💯2

18 Oct 2026, 12:59 UTC≈6,570 views141 reactionsread 19 October 2026
Video

Ну готовы к следующей рабочей недели ?

❤100❤‍🔥21😍13custom 52805699744049666393💋2💅1💘1

18 Oct 2026, 10:30 UTC≈7,510 views192 reactionsread 19 October 2026
Video

Когда Насте бывает грустно , все вокруг знают подари ей цветочек 😃🌸и ее опять будет не остановить , не поймать , не замедлить , не обидеть

❤130❤‍🔥38🎉14custom 52805699744049666397🙊2🤩1

16 Oct 2026, 10:34 UTC≈10,400 views276 reactionsread 19 October 2026
Video

Ну девки , под конец недели прям сложно 😣

❤196custom 528056997440496663932🤩23❤‍🔥8custom 52558617963502240635🎄4👍4💘4

15 Oct 2026, 16:32 UTC≈11,900 views189 reactionsread 19 October 2026
Video

Девки , Антон сломался на первом пункте 😂 я с вами согласна «Лечение Зубов 🆓 😂

custom 528056997440496663987❤‍🔥64🤩26😎6😈3😴2❤1

15 Oct 2026, 13:30 UTC≈11,700 views196 reactionsread 19 October 2026
Video

Что он в желтом это совпадение 😂😂😂

❤‍🔥119🤩32❤28🍓10custom 52805699744049666395🆒2

15 Oct 2026, 12:24 UTC≈11,300 views173 reactionsread 19 October 2026
Video

В этот день я помню каждую мелочь 🥹 для меня был взрыв по эмоциям 😃

❤‍🔥98❤40😍22👀6💘3🎄2💋1custom 52805699744049666391

15 Oct 2026, 10:58 UTC≈11,300 views153 reactionsread 19 October 2026
Video

Идеально 😍

❤112❤‍🔥17💘13custom 528056997440496663911

15 Oct 2026, 08:47 UTC≈11,400 views326 reactionsread 19 October 2026
Video

😃 на озоне заказала . Жизнь упрощает , дети не боятся 😬. Но надо прям приловчится им пользоваться 🤨 в частных наверно уже давно такие используют 😃

❤‍🔥203❤81😍22💯13👍6custom 52805699744049666391

14 Oct 2026, 06:49 UTC≈11,900 views69 reactionsread 19 October 2026
Photo

Мой идеальный завтрак — это наивкуснейший кофе в зернах Poetti Daily, нежные сырники, творожная запеканка или тыквенная каша 🥞☕️ Просто моя любоооовь! Всё это я заказываю в Самокате и каждый раз радуюсь качеству продуктов! Но за привычными любимыми вкусами стоит гораздо больше, чем кажется на первый взгляд 👀 Команда Самоката тщательно выбирает производителей, пробует сотни продуктов,проверяет их в лабораториях и ул…

❤57❤‍🔥7😢4💘1

13 Oct 2026, 15:02 UTC≈11,600 views272 reactionsread 19 October 2026
Photo

Подборка одежды из предыдущего видео! Галстук Куртка Шорты Рубашка Казаки высокие на каблуке Сумка ❤️ - очень нравится! 💯 - интересно) 🍓 - совсем не мое

❤204💯46❤‍🔥22

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

Posts edited after publishing

@laprosco edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
6 September 2026
Most recent edit
6 September 2026

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

“Nastasyakoba” (@laprosco), 49,101 subscribers as measured 19 October 2026. Telegram Register, tgregister.com/channel/laprosco.

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.