9 Apr 2026, 23:58 UTC87 viewsread 14 August 2026
@n0lxs обожаю, меня радует что все быстро и без скама!!
Signed 0X
Channel
𝓢ϯᴏℝė 𝒪𝚇
@store_0xs
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
300subscribers
-2 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002748721481 |
|---|---|
| Type | Channel |
| Username | @store_0xs |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/store_0xs |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 10:06 | 300 | -2 |
| 14 Aug 2026, 10:02 | 302 | first reading |
Engagement
14 posts held, back to 5 April 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 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 14 posts for this entry, the most recent from 9 April 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2s
- Average length
- 2s
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.
Recent posts
9 Apr 2026, 23:58 UTC86 viewsread 14 August 2026
Photo
✨〽️〽️🦋🦋🦋#𝗽𝗿𝗼𝗼𝗳 〽️〽️✨ Благодарю вас за доверие!! 🔵ник в рб: k0itys 🔵юз: @n0lxs 🤩᧐ᴛɜыʙ
Signed 0X
9 Apr 2026, 23:56 UTC73 viewsread 14 August 2026
Photo
@n0lxs не скам, купил тончики, все пришло быстро, советую🩸🩸🩸🩸
Signed 0X
9 Apr 2026, 23:56 UTC59 viewsread 14 August 2026
Photo
✨〽️〽️🦋🦋🦋#𝗽𝗿𝗼𝗼𝗳 〽️〽️✨ Благодарю вас за доверие!! 🔵ник в рб: k0itys 🔵юз: @n0lxs 🤩᧐ᴛɜыʙ
Signed 0X
5 Apr 2026, 21:17 UTC66 viewsread 14 August 2026
@n0lxs обожаю, буду покупать еще
Signed 0X
5 Apr 2026, 21:17 UTC59 viewsread 14 August 2026
Photo
✨〽️〽️🦋🦋🦋#𝗽𝗿𝗼𝗼𝗳 〽️〽️✨ Благодарю вас за доверие!! 🔵ник в рб: k0itys 🔵юз: @n0lxs 🤩᧐ᴛɜыʙ
Signed 0X
5 Apr 2026, 00:26 UTC44 viewsread 14 August 2026
легенда просто @n0lxs
Signed 0X
5 Apr 2026, 00:26 UTC36 viewsread 14 August 2026
@n0lxs супер,не обманула!
Signed 0X
5 Apr 2026, 00:26 UTC34 viewsread 14 August 2026
Photo
✨〽️〽️🦋🦋🦋#𝗽𝗿𝗼𝗼𝗳 〽️〽️✨ Благодарю вас за доверие!! 🔵ник в рб: k0itys 🔵юз: @n0lxs 🤩᧐ᴛɜыʙ
Signed 0X
5 Apr 2026, 00:26 UTC22 viewsread 14 August 2026
Photo
@n0lxs Ну моя, как всегда все шикарно, не скам
Signed 0X
5 Apr 2026, 00:26 UTC27 viewsread 14 August 2026
Photo
✨〽️〽️🦋🦋🦋#𝗽𝗿𝗼𝗼𝗳 〽️〽️✨ Благодарю вас за доверие!! 🔵ник в рб: k0itys 🔵юз: @n0lxs 🤩᧐ᴛɜыʙ
Signed 0X
5 Apr 2026, 00:26 UTC63 viewsread 14 August 2026
@n0lxs четко ,не Скам! спасибо большое за понимание
Signed 0X
Showing the 12 most recent of 14 posts we hold for @store_0xs. 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.
Citation-graph rank
Citation-graph rank — 1,362,389 of 1,478,351entries 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“𝓢ϯᴏℝė 𝒪𝚇” (@store_0xs), 300 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/store_0xs.
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.