Channel
@eisasinfo
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
3subscribers
+1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002280165780 |
|---|---|
| Type | Channel |
| Username | @eisasinfo |
| Created | 19 February 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 6 October 2026 |
| On Telegram | t.me/eisasinfo |
Ecommerce storefront — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 3 October 2026 and assigned it the closest of 31 fixed categories, at 52% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 14:18 | 3 | +1 |
| 14 Aug 2026, 06:16 | 2 | no change |
| 9 Aug 2026, 11:46 | 2 | first reading |
10 posts held, back to 19 February 2025 — 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 10 posts for this entry, the most recent from 29 March 2025. An engagement rate over an empty window would be a number about nothing.
ㅤ ✿ . ⩇ carrd commi form : ㅤ · theme : · type of design : · rush or not : · inspo : · color palette : · additional requests : · full or half payment : · do I provide the layout? ( y or n ) : · content/s or info/s needed : ⌗ ・ dm @aprxcity for orders
ㅤ ✿ . ⩇ discord bot command/s form : ㅤ · theme : · rush or not : · color palette : · full or half payment : · do I provide the layout? : ( y or n ) · server link : ㅤ · commands : 1. 2. 3. ㅤ · auto responders : 1. 2. 3. ⌗ ・ dm @aprxcity for orders
ㅤ ✿ . ⩇ discord bot commi form : ㅤ · theme : · rush or not : · color palette : · bot pfp & banner : · bot's about me : · full or half payment : · shop or community server bot : · do I provide the layout? : ( y or n ) · server link : ㅤ · commands : 1. 2. 3. 4. 5. 6. 7. 8. ㅤ · auto responders : 1. …
ㅤ ✿ . ⩇ discord server commi form : ㅤ · theme : · type of design : · rush or not : · inspo : · shop or community sv : · custom inclusions : · full or half payment : · do I provide the layout? : ( y or n ) · type of server commission : ( revamp or custom ) ⌗ ・ dm @aprxcity for orders
ㅤ ✿ . ⩇ line emojis / stickers form : ㅤ · quantity : · animated or static : · stickers or emojis link/s : get ur stickers / emojis here ⌗ ・ dm @aprxcity for orders
ㅤ ✿ . ⩇ other editing commi form : ㅤ · theme : · size : · type of design : · type of commission : · rush or not : · font or font combo : · theme / pic bg : · inspo : · color palette : · additional requests : · full or half payment : · phrases or info needed : ⌗ ・ dm @aprxcity for orders
ㅤ ✿ . ⩇ sticker commissions : ㅤ · name of stix pack : · sticker style : · rush or not : · inspo : · color palette : · additional requests : · full or half payment : · fonts (input code/s) : · phrases + (1) emoji for each sticker : click here for color palette and for fonts ⌗ ・ dm @aprxcity for orders ㅤ
Sticker, posted without a caption
ㅤ ▹﹕천사﹒commission forms . reminder to completely answer the forms to avoid misunderstandings. ⩇ . navigation : · sticker comms · other editing comms · line emojis / stickers · discord server comms · discord bot comms · discord bot commands ㅤ ㅤ
Channel created
Showing the 10 most recent of 10 posts we hold for @eisasinfo. 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.
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.
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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“⊹ ۪ . 𝘖rder forms ˳ ۫” (@eisasinfo), 3 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/eisasinfo.
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.