Hi.
custom 60777039387636548993

Channel
@MarkForces
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
59subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002146193452 |
|---|---|
| Type | Channel |
| Username | @MarkForces |
| Description | ㅤㅤ ⓘ : SOVEREIGN REVERENCE───801. In the era 1999 gesture of respect, bid someone welcome. We are MARK FORCE; M4CE, Together We Rise. Au Revoir! Contact: @MarkForcesBot Archive: @ArsipMarkForce |
| Created | Between 1 November 2023 and 17 March 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 1 |
| On Telegram | t.me/MarkForces |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 01:16 | 59 | first reading |
12 posts held, back to 17 March 2024 — 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 12 posts for this entry, the most recent from 15 June 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 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.
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.
30 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6077703938763654899 | 30 | 100.0% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 5 of the 12 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 30reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 17 March 2024 to 15 June 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Hi.
custom 60777039387636548993
Stop being sad and start loving yourself and me (LOLL). That's the joke, ✌🏻. #MARKLEE 💥 Weibo Update. ±
custom 607770393876365489910
Sticker, posted without a caption
“God's Masterpiece 99's” / MARKFORCE . . pinned «📢 $8,00 [] The Spend For “MARK FORCE 𖢵 OPEN HOUSE” E ¢. Ist (Re: No Fools) area: “Wh—? MarkForce. territory” ... 10/04 [ ‼️ ] 𐂡. COME HITHER! The halls methaporic and obstacles to occasion enlivening to all mankind and will make the cosmos intensification…»
📢 $8,00 [] The Spend For “MARK FORCE 𖢵 OPEN HOUSE” E ¢. Ist (Re: No Fools) area: “Wh—? MarkForce. territory” ... 10/04 [ ‼️ ] 𐂡. COME HITHER! The halls methaporic and obstacles to occasion enlivening to all mankind and will make the cosmos intensification to scintillate, like formerly / Destination Had. ⤵️ [https://t.me/+LHUT3kZBSwU4MDI1]
custom 60777039387636548992
Good morning. Don't forget to drink some water and stay healthy, everyone. 😉
custom 607770393876365489914
Sticker, posted without a caption
💅 @BratzYins × @predizer × @cordeliacosette × @markforces × @rosyfloriest ㅤ ۪ ˚. 𐙚── ❤️ Step into the world of Bratz where bold fashion statements and unapologetic attitude reign supreme! From chic street styles to glamorous evening looks, our collaboration brings the iconic BratzYins vibe to life like never before. Get ready to slay every sidewalk with confidence and style! ꣑୧ ׁ ₊ XoXo Bratzyins 👧💋
custom 60777039387636548991
Sticker, posted without a caption
People have been asking and annoying, so shut it with a good things—music. @/onyourm_ark 💥 Instagram Update. ±
Sticker, posted without a caption
Theres—something you've been searching for, the missing color that could bring your happiness ; yellow. 🪷 @/onyourm_ark 💥 Instagram Update. ±
Showing the 12 most recent of 12 posts we hold for @MarkForces. 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 — 763,089 of 1,169,250entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
““God's Masterpiece 99's” / MARKFORCE . .” (@MarkForces), 59 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/MarkForces.
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.