Telegram RegisterThe public register of Telegram
Telegram profile photo for База Баяни(ЩИТПОСТЫ)

Channel

База Баяни(ЩИТПОСТЫ)

@Waxwell_TRUE

On this record: Previous handles · Growth · Engagement · What this channel posts · Posts · Cite this entry

17subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003981929926
TypeChannel
Username@Waxwell_TRUE
DescriptionЧто-то интересное
Created30 May 2026 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live25 August 2026
Measurements held2
On Telegramt.me/Waxwell_TRUE

Previous handles

@Waxwell_TRUE was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@Waxwell_TRUE
held 11 August 2026 – 11 August 2026

Growth

1710 Aug 2026, 16:00 — 17 subscribers11 Aug 2026, 20:46 — 17 subscribers10 Aug 2026, 16:0011 Aug 2026, 20:46
2 measurements spanning 1 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 16–18 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 20:4617no change
10 Aug 2026, 16:0017first reading

Engagement

7 posts held, back to 30 May 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 7 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1

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

Recent posts

26 Jul 2026, 12:19 UTC64 viewsread 11 August 2026

Если хотите отправить свою дичь для Баяни, вот вам бот - @BayaniHOPCoo_bot

20 Jul 2026, 13:05 UTC40 viewsread 11 August 2026
Photo

Доверие - насколько вам доверяет Баяни. ≻───── ⋆✩⋆ ─────≺ Доверие может уменьшатся (негативное общение) или наоборот повышатся (позитивное общение) либо оставатся нейтральным (обычное общение). ≻───── ⋆✩⋆ ─────≺ На доверие влияют: • вид вашего персонажа • Характер вашего персонажа • Общение • Фандом (доверие похожих фд значительно больше) • Схожесть персов (Потом ещё чота напишу сюда)

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

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

“База Баяни(ЩИТПОСТЫ)” (@Waxwell_TRUE), 17 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Waxwell_TRUE.

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.