File, posted without a caption
custom 538888831517066567584custom 514809322857824400952custom 545638970482178905819custom 51048753177307396229

Channel
@ampulakapeli
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Cite this entry
5,439subscribers
+56 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001840979058 |
|---|---|
| Type | Channel |
| Username | @ampulakapeli |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/ampulakapeli |
Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 12 August 2026 and assigned it the closest of 31 fixed categories, at 55% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
6,540 average views per post against 5,416 subscribers — an engagement rate of 120.7%. Across the 40,483 registered channels in the same cohort — 3,163–9,999 subscribers, posting mainly in Russian — the middle half sit between 7.15% and 26.5%, with a median of 14.2%.
| Window | 30 days (13 July 2026 – 12 August 2026) |
|---|---|
| Posts measured | 8 of 8 published in the window (0 exact, 8 rounded by Telegram) |
| Views totalled | 52,310 |
| Mature posts only | 120.7% over 8 posts read at least 24h after publication |
| Subscribers | 5,416 measured 11 August 2026 |
| Cohort | b3162:rus · 40,483 channels · p10 3.46% · p25 7.15% · p50 14.2% · p75 26.5% · p90 43.8% |
| Position in cohort | 99.397th percentile · 8.5× the cohort median |
| Uncertainty | ±0.057% of the figure, from Telegram’s rounding |
| Post language | Russian · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 05:47 | 5,439 | +23 |
| 11 Aug 2026, 08:36 | 5,416 | +28 |
| 8 Aug 2026, 19:08 | 5,388 | +5 |
| 7 Aug 2026, 19:18 | 5,383 | no change |
| 7 Aug 2026, 19:05 | 5,383 | first reading |
15 posts held, back to 18 March 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 8 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 15 (18 March 2026 – 9 August 2026) |
| Views total | 45,670 |
| Reactions total | 1,432 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 05:26 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.
Measured directly from 2 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.
3,557 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 32.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5388888315170665675 | 1,143 | 32.1% | |
| custom 5148093228578244009 | 1,078 | 30.3% | |
| custom 5456389704821789058 | 865 | 24.3% | |
| custom 5388862223244341650 | 312 | 8.77% | |
| custom 5104875317730739622 | 159 | 4.47% |
Custom emoji. Every row above is a 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 areTelegram’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 15 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 3,557reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 18 March 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ampulakapeli. 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 15 most recent posts we hold for this entry, published 18 March 2026 to 9 August 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.
File, posted without a caption
custom 538888831517066567584custom 514809322857824400952custom 545638970482178905819custom 51048753177307396229
Photo, posted without a caption
custom 5148093228578244009210custom 545638970482178905864custom 538888831517066567533custom 510487531773073962218
Video, posted without a caption
custom 5388888315170665675164custom 5148093228578244009110custom 545638970482178905858custom 510487531773073962221
https://youtu.be/3d12tcYEQ2Q?si=Hr6I5KkkPfUfVnvD
custom 5456389704821789058141custom 514809322857824400951custom 538888831517066567521custom 51048753177307396229
Video, posted without a caption
custom 5148093228578244009107custom 538888831517066567528custom 545638970482178905819custom 51048753177307396226
“AMPULA KAPELI" AUTUMN-SPRING 2024 MOSCOW SAINT-PETERSBURG EKATERINBURG MINSK FRIDAY/24.07 HTTPS://YOUTUBE.COM/@AMPULAKAPELI
custom 545638970482178905870custom 514809322857824400922custom 51048753177307396225custom 53888883151706656752
Photo, posted without a caption
custom 514809322857824400976custom 538888831517066567516custom 545638970482178905812custom 51048753177307396225
В Санкт Петербурге есть место, за пределами сети, где можно обрести шкурки ампула капель. Заходите, ищите, спрашивайте. Как монах, который ищет тишину в шумном рынке, найдите то, что ищете.
custom 5456389704821789058238custom 538888831517066567539custom 510487531773073962233custom 514809322857824400921
ampulakapeli.ru
custom 5388862223244341650142custom 545638970482178905841custom 514809322857824400940custom 51048753177307396229custom 53888883151706656753
ampulakapeli.ru
custom 5388862223244341650167custom 514809322857824400978custom 545638970482178905838custom 538888831517066567512custom 510487531773073962211
Да это жёстко Лошадки будут на сайте
custom 5148093228578244009280custom 538888831517066567551custom 545638970482178905843custom 51048753177307396227custom 53888622232443416501
https://t.me/boost/ampulakapeli
custom 538888831517066567527custom 54563897048217890588custom 51048753177307396223custom 53888622232443416501
Showing the 12 most recent of 15 posts we hold for @ampulakapeli. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“КАПЕЛЬ” (@ampulakapeli), 5,439 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ampulakapeli.
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.