Telegram RegisterThe public register of Telegram

Channel

Бисероплетение🍄:>

@sxemku

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

1subscribers

+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-1001682301829
TypeChannel
Username@sxemku
DescriptionЗдесь схемы для бисероплетение:> :) :]
Created5 February 2022measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/sxemku

Growth

17 August 2026 — 1 subscribers14 August 2026 — 1 subscribers7 August 202614 August 2026
2 measurements spanning 7 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:171no change
7 Aug 2026, 08:541first reading

Engagement

8 posts held, back to 5 February 2022the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 5 February 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
15
Links
1

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

5 Feb 2022, 23:01 UTC326 viewsread 14 August 2026
Photo

И вот дольче Милки кому надо и кто искал

5 Feb 2022, 22:58 UTC327 viewsread 14 August 2026
Photo

Вот уточки (я незнаю как она называются) :>

5 Feb 2022, 22:56 UTCviews —

Бисероплетение🍄:> pinned «И да я беру схемы у https://t.me/schemesforbeading и также у https://t.me/beadbeam и из пинтреста»

5 Feb 2022, 22:55 UTC254 viewsread 14 August 2026

И да я беру схемы у https://t.me/schemesforbeading и также у https://t.me/beadbeam и из пинтреста

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

Mentions

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

“Бисероплетение🍄:>” (@sxemku), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/sxemku.

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.