Channel
@pivovarmemeverse
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
697subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002181772394 |
|---|---|
| Type | Channel |
| Username | @pivovarmemeverse |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/pivovarmemeverse |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 00:18 | 697 | -1 |
| 31 Aug 2026, 02:24 | 698 | -2 |
| 24 Aug 2026, 15:17 | 700 | +1 |
| 16 Aug 2026, 15:45 | 699 | -2 |
| 8 Aug 2026, 02:18 | 701 | no change |
| 7 Aug 2026, 22:44 | 701 | first reading |
20 posts held, back to 11 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.
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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
1,525 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 36.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5248946752974762139 | 551 | 36.1% | |
| custom 5336951869820398133 | 545 | 35.7% | |
| custom 5265034613838871330 | 123 | 8.07% | |
| 👻 | 93 | 6.10% | |
| custom 5336808151624739318 | 82 | 5.38% | |
| custom 5271873206796425878 | 57 | 3.74% | |
| custom 5201728239004827919 | 50 | 3.28% | |
| custom 5359360393535828595 | 12 | 0.787% | |
| custom 5359484191673167746 | 12 | 0.787% |
Custom emoji. 8 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 20 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 1,525 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 11 July 2026 to 4 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.
Реальное фото меня, когда я вижу, что на канал подписался кто-то со смешными авами и статусом (убедительная просьба сменить их на что-то несмешное и скучное в случае, если вдруг решите отписаться 😠)
custom 524894675297476213947custom 533695186982039813317custom 52650346138388713306
Невыдуманная история о том, куда пропала Героиня Ферелдена
custom 533695186982039813359custom 524894675297476213924custom 52650346138388713305custom 53368081516247393183
простите
custom 524894675297476213938custom 535936039353582859512custom 535948419167316774612
Возвращаемся к истокам
custom 524894675297476213959custom 533695186982039813313custom 52650346138388713305
Photo, posted without a caption
custom 524894675297476213964custom 526503461383887133013custom 53368081516247393189
Posted without readable text
custom 52489467529747621394custom 53369518698203981332
Photo, posted without a caption
custom 527187320679642587847custom 524894675297476213916custom 53369518698203981335custom 53368081516247393184
Поддержу Всемемную
custom 533680815162473931847custom 524894675297476213916custom 52650346138388713302custom 52718732067964258781
Когда Морриган опять сказала "смех без причины - признак дурачины"
custom 533695186982039813351custom 52650346138388713304custom 52718732067964258781
Photo, posted without a caption
custom 524894675297476213981custom 533695186982039813313custom 53368081516247393189custom 52650346138388713304
okay man jeez just calm down man
custom 533695186982039813344custom 524894675297476213912custom 52650346138388713303custom 52718732067964258781
Душераздирающие кадры нападения саларианцев на базу гетов, Вермайр, 2183 год
custom 524894675297476213951custom 533695186982039813312custom 52718732067964258782
Showing the 12 most recent of 20 posts we hold for @pivovarmemeverse. 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Всемемная” (@pivovarmemeverse), 697 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/pivovarmemeverse.
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.