Telegram RegisterThe public register of Telegram
Telegram profile photo for literacy

Channel

literacy

@septbae

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

1subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003783522623
TypeChannel
Username@septbae
Description‎ @sewpia celestial commotion mellifluous murmur a gossamer cadence suspended between fleeting inhalations honeyed ♡. ‌‌‌‎
CreatedBetween 1 February 2026 and 14 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live9 September 2026
Measurements held2
On Telegramt.me/septbae

Growth

18 August 2026 — 1 subscribers14 August 2026 — 1 subscribers8 August 202614 August 2026
2 measurements spanning 6 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, 10:021no change
8 Aug 2026, 05:031first reading

Engagement

20 posts held, back to 14 June 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Links
4

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 Aug 2026, 08:00 UTC16 viewsread 14 August 2026

akuloo sakit hati udah jawab sebaik mungkin, terus akhirnya di read gitu aja🥺

5 Aug 2026, 07:54 UTC14 viewsread 14 August 2026

biasain berkabar tolong... kalau ngga jadi gapapa ko temen-temen, bilang aja "sabine maaf ngga jadi" aku gabakal gigit juga lagian😐

22 Jul 2026, 10:38 UTC89 viewsread 14 August 2026

tolong jangan bawa rekber clone, di aku ngga akan mempan jadinya buang² waktu kalian juga 🌷

14 Jun 2026, 09:44 UTC270 viewsread 14 August 2026

‎‌‌‌‎ 𝟷𝟽 / à 🧂.. amidst a world forever rushing beneath hurried skies and restless clocks (✶) this place remains a small pause between heartbeats a fleeting sanctuary where slowing down feels permissible again. delicate lantern illuminating the path ahead, making every page little detail easier to embrace ♥︎ ‌‌‌‎

14 Jun 2026, 09:43 UTC242 viewsread 14 August 2026

‎ little hours where this miniature world slowly awakens where daylight arrives in honey-soft streams and quiet rhythms begin stretching across the atmosphere 🪷. .   𐀶 weekdays 10.00 – 20.00   𐀶 weekends 08.00 – 22.00 ( ౨ৎ. ) iii—when replies begin drifting more slowly beneath evening skies or midnight stillness, think of it as the world beyond the screen softly calling for its…

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

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.

#1 𝗦𝗔𝗩𝗢𝗥𝗘 𝗕𝗔𝗦𝗘
@savorebase · 4061 post

Names

Channels on the register whose handles appear in this channel's posts.

4.04 ♡︎ 𝓟ayment ! xo. dwelt 🎀
@paysbine · 22 postsARCHIVE RESSELLER ACEBILIS
@acebiliss · 281 post𝒞herumie : open apprem, teleprem, stars, robux, jaspin & nokos ♡
@cherumiee · 9551 postproof sabine
@proofsbine · 41 post₊˚⊹ᰔ 𝘴𝘰𝘶𝘳𝘭𝘶𝘪𝘯𝘦 : close <𝟑 .ᐟ
@sourluine · 1681 post🎀💬 pastel loveletter.xo !3° .˃ᴗ˂ マ ? bunny soft blush atmosphere & tiny comforting sparkles ᡣ • . • 𐭩 ♡
@sparkelc · 41 postMINIMAL RNK
@wajibrnk · 2,5881 post

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.

“literacy” (@septbae), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/septbae.

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.