Telegram RegisterThe public register of Telegram

Channel

гистамин

@gistamine

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

676subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001703354944
TypeChannel
Username@gistamine
DescriptionВконтакте: vk.com/histamine Я.Музыка: clck.ru/39gfRc TikTok: tiktok.com/@gistamine
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/gistamine

Growth

6767 Aug 2026, 06:48 — 676 subscribers7 Aug 2026, 07:01 — 676 subscribers7 Aug 2026, 06:487 Aug 2026, 07:01
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 675–677 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 07:01676no change
7 Aug 2026, 06:48676first reading

Engagement

20 posts held, back to 19 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
59.6%
avg views ÷ 676 subscribers
Avg views / post
403
5 posts measured
Reaction rate
5.91%
reactions ÷ views · ER floor
Posts in window
5
of 20 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 30 July 2026
Posts held20 (19 May 202630 July 2026)
Views total2,014
Reactions total119
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 07:01 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

Photos
190
Videos
89
Links
201

Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

597 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 35.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 537105284929369723521435.8%
custom 546310171650321568121235.5%
custom 537104201738617656617128.6%

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 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 597reactions 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 19 May 2026 to 30 July 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
146
across the posts below
Posts paid on
16
of 20 we hold a reading for · 80%
Most on one post
60
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @gistamine. 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 20 most recent posts we hold for this entry, published 19 May 2026 to 30 July 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.

Recent posts

30 Jul 2026, 21:00 UTC413 views21 reactions60 Starsread 7 August 2026
Photo

Премьера трека! гистамин - love me like a runaway Слушать на площадках музыка: tokyo noire припев: Дмитрий Каримов сведение: сто сорок три обложка: гистамин лейбл: NORD Side поддержать через: Яндекс.Чаевые спасибо Жене Мильковскому

custom 537104201738617656611custom 53710528492936972357custom 54631017165032156813

27 Jul 2026, 13:00 UTC376 views26 reactions4 Starsread 7 August 2026
Video

love me like a runaway 31.07 dir: olezha md: Валерия Кононенко

custom 537104201738617656614custom 54631017165032156817custom 53710528492936972355

24 Jul 2026, 14:40 UTC426 views23 reactions1 Starread 7 August 2026
Photo

ДЕНЬГИ ЗА ПРЕСЕЙВ победитель получит 1000₽ 1. сделай пресейв по ссылке 2. отправь скриншот в комментарии жди результатов 31 июля

custom 537104201738617656611custom 54631017165032156817custom 53710528492936972355

24 Jul 2026, 14:40 UTC374 views24 reactions4 Starsread 7 August 2026
Video message

Video message, posted without a caption

custom 537105284929369723512custom 54631017165032156817custom 53710420173861765665

23 Jul 2026, 15:00 UTC425 views25 reactions4 Starsread 7 August 2026

ПРЕСЕЙВ

custom 546310171650321568115custom 53710528492936972357custom 53710420173861765663

2 Jul 2026, 21:00 UTC732 views40 reactions10 Starsread 7 August 2026
Photo

Премьера трека! гистамин - домой Слушать на площадках музыка: tokyo noire сведение: сто сорок три обложка: гистамин лейбл: NORD Side поддержать через: Яндекс.Чаевые платный канал: купить доступ

custom 546310171650321568121custom 537105284929369723512custom 53710420173861765667

2 Jul 2026, 11:50 UTC568 views14 reactionsread 7 August 2026
Photo

СЕГОДНЯ ДОМОЙ скину трек случайному комментатору этого поста уже через несколько часов успей сделать пресейв

custom 53710528492936972358custom 53710420173861765663custom 54631017165032156813

1 Jul 2026, 15:00 UTC609 views37 reactions5 Starsread 7 August 2026
Video

домой 03.07

custom 537104201738617656618custom 546310171650321568111custom 53710528492936972358

22 Jun 2026, 18:30 UTC750 views28 reactions4 Starsread 7 August 2026

ПРЕСЕЙВ

custom 537105284929369723515custom 54631017165032156817custom 53710420173861765666

5 Jun 2026, 09:15 UTC784 views22 reactions5 Starsread 7 August 2026
Photo

если хотите поддержать релиз: 1. оставьте лайк и коммент под постом с релизом в VK 2. поставьте лайк релизу и артисту на Яндекс.Музыке 3. репостните пост с релизом в свой телеграмм канал, если такой имеется 4. отправьте донат через Яндекс.Чаевые или подпишитесь на закрытый канал

custom 537105284929369723511custom 54631017165032156817custom 53710420173861765664

4 Jun 2026, 21:00 UTC≈1,620 views46 reactions11 Starsread 7 August 2026
Photo

Премьера релиза! гистамин, TERNOVA - перегорел 2 Слушать на площадках музыка: tokyo nóire, anri, noireees, sympholic, pxntacle сведение: сто сорок три обложка: гистамин анимация: sarcxma лейбл: NORD Side сторис для поддержки поддержать через: Яндекс.Чаевые платный канал: купить доступ

custom 537105284929369723528custom 53710420173861765669custom 54631017165032156819

4 Jun 2026, 20:55 UTC541 views19 reactions5 Starsread 7 August 2026
Video

сторис для поддержки

custom 537104201738617656612custom 53710528492936972354custom 54631017165032156813

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

Citation-graph rank

Citation-graph rank — 49,718 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

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

“гистамин” (@gistamine), 676 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/gistamine.

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.