Telegram RegisterThe public register of Telegram

Channel

альтер рейсо

@Reiso_channel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

150subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002165253786
TypeChannel
Username@Reiso_channel
DescriptionтевирП отэ тра ланак йокат йотурк ыносреп как осйеР Пинтерест: https://pin.it/4A5FsvZ0x Буст: https://t.me/boost/Reiso_channel Щп канал: https://t.me/+adzhgMs4vNRlMzNi Лс: @ReisoChan
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/Reiso_channel

Growth

1506 August 2026 — 150 subscribers8 August 2026 — 150 subscribers6 August 20268 August 2026
2 measurements spanning 2 days. 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 149–151 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 19:47150no change
6 Aug 2026, 20:17150first reading

Engagement

16 posts held, back to 1 July 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
136.3%
avg views ÷ 150 subscribers
Avg views / post
205
10 posts measured
Reaction rate
4.55%
reactions ÷ views · ER floor
Posts in window
12
of 16 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 6 August 2026
Posts held16 (1 July 20266 August 2026)
Views total2,045
Reactions total93
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 19:47 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
322
Videos
18
Links
92

Lifetime counters from Telegram’s own channel header, read 8 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.

Video runtime
12s
Average length
12s

Measured directly from 1 video 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

139 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 43.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53462190262656779296043.2%
🦄2417.3%
custom 53463145892880145492014.4%
custom 53460744276017218261510.8%
custom 520196276139907333553.60%
😈53.60%
custom 539551473244887237632.16%
custom 543816297171914130732.16%
👾21.44%
custom 537780944273567730510.719%
custom 543179304559289263910.719%

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 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 14 of the 16 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 139reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 1 July 2026 to 6 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.

Recent posts

6 Aug 2026, 10:01 UTC51 views11 reactionsread 8 August 2026
Photo

🐶🛼👽🐇 Для... @N00863 🌨️🌨️🌨️🌨️🌨️🌨️🌨️ — Напоминаю что у меня открыты предзаказики по бискас мерчу! (с низкими ценами) 🌨️🌨️🌨️🌨️🌨️🌨️🌨️ #полноценка

custom 52019627613990733354custom 54381629717191413073custom 53955147324488723762custom 53778094427356773051custom 54317930455928926391

3 Aug 2026, 16:16 UTC79 views7 reactionsread 8 August 2026
Photo

👽™️🌰⛽️👽- арт человека под номером 3 ichigowarano оn X!! — Ну да я дазай манипулятор заставила вас всех нажать на 4 муахаах... Ии слоп брала из Стейбл Вайфу и Пиксаи Аи Победитель пишет в лс @ReisoChan с пруфами гс ➿➿➿➿➿➿➿➿

custom 53463145892880145495custom 52019627613990733351custom 53955147324488723761

31 Jul 2026, 11:23 UTC126 views5 reactionsread 8 August 2026

Posted without readable text

custom 53462190262656779292custom 53463145892880145492😈1

31 Jul 2026, 11:03 UTC125 views12 reactionsread 8 August 2026
Photo

🐈🤰🤰 Для.. @Irealchik 🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️ — Го добьем реактов на этом посте, осталось совсем чуть чуть!! 🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️ #заказ #полноценка

custom 53462190262656779297👾2🦄2custom 53463145892880145491

30 Jul 2026, 06:21 UTC122 views1 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

custom 53462190262656779291

25 Jul 2026, 10:35 UTC180 views8 reactionsread 8 August 2026
Photo

➿ПРЕДЗАКАЗЫ БИСКАС МЕРЧ➿ 🌟ПРЕДЗАКАЗЫ с 25.07 по 25.08 Готовность и отправка мерча примерно в октябре-ноябре Доставка озон; СДЭК, Яндекс, Почта России.(оплачивается отдельно перед отправкой) Предоплата на т-банк По вопросам и заказам писать в лс @ReisoChan Тгк: @Reiso_channel Важно: Я делаю возвраты только при наличии брака. Пожалуйста, уведомите родителей о своей покупке, чтобы избежать недоразумений. На картинках пр

🦄7custom 53462190262656779291

25 Jul 2026, 08:01 UTC506 views5 reactionsread 8 August 2026

Posted without readable text

custom 53462190262656779295

21 Jul 2026, 12:10 UTC266 views36 reactionsread 8 August 2026
Photo

🤩Cutie Madoka 🎀 😀😀😀😀😀😀😀😀 — Продолжаю серию артов с ленточками от Ядерного Танка — На 35рк спидпеинт!! 😀😀😀😀😀😀😀😀 💋 #фанарт #полноценка

🦄15custom 534621902626567792910custom 53460744276017218267custom 53463145892880145494

18 Jul 2026, 17:28 UTC346 views3 reactionsread 8 August 2026
Poll

Внезапный дэб — если я буду делать мерч по Бискасу, вы будете это покупать?

  1. Нет29%
  2. Да13%
  3. Я подумаю21%
  4. У меня нет денег37%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

custom 53462190262656779293

18 Jul 2026, 12:05 UTC244 views5 reactionsread 8 August 2026
Photo

🔤🔤🔤 для... @irlHyposelenia 😀😀😀😀😀😀😀😀😀😀 — One more commission, работаем. 😀😀😀😀😀😀😀😀😀😀 #заказ #полноценка

😈2custom 53462190262656779292custom 53463145892880145491

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

18 Jul 2026, 17:28 UTCFinal Results84 voters

Внезапный дэб — если я буду делать мерч по Бискасу, вы будете это покупать?

  1. Нет29%
  2. Да13%
  3. Я подумаю21%
  4. У меня нет денег37%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 16 most recent posts we hold, published 1 July 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 213,324 of 1,350,102entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“альтер рейсо” (@Reiso_channel), 150 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Reiso_channel.

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.