Telegram RegisterThe public register of Telegram
Telegram profile photo for Sapphire

Channel

Sapphire

@sapphiregnm

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

507subscribers

-4 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002199573679
TypeChannel
Username@sapphiregnm
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/sapphiregnm

Topic

Science — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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.

Growth

5055115086 August 2026 — 511 subscribers6 August 2026 — 511 subscribers14 August 2026 — 505 subscribers23 August 2026 — 506 subscribers29 August 2026 — 510 subscribers8 September 2026 — 507 subscribers5076 August 20268 September 2026
6 measurements spanning 33 days, net -4. 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”. The vertical axis spans 504–512 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 16:40507-3
29 Aug 2026, 12:53510+4
23 Aug 2026, 10:12506+1
14 Aug 2026, 21:08505-6
6 Aug 2026, 18:33511no change
6 Aug 2026, 08:15511first reading

Engagement

11 posts held, back to 30 June 2026the 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 11 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

36 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1850.0%
🔥616.7%
😭411.1%
👍38.33%
😁38.33%
💔25.56%

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 10 of the 11 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 30 June 2026 to 30 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

30 Jul 2026, 10:13 UTC111 views4 reactionsread 6 August 2026
Forwarded from @kurgantisttPhoto

Genetics of the English by era @steppelander

🔥4

22 Jul 2026, 21:48 UTC310 views1 reactionsread 6 August 2026
Photo

half of the J2 carriers are from indian subcontinent and only %20 is from middle east

1

7 Jul 2026, 15:50 UTC417 views1 reactionsread 6 August 2026
Forwarded from @SteppeArchivePhoto

Y-DNA & mtDN Haplogroups for Turkic & non-Turkic Speaking Groups Turkic: Kyrgyz, Uzbek, Karakalpak, Karluks from Khatlon region in Tajiktsan, Uyghur, Turkmen non-Turkic: Hazara, Tajik Dungan Source (Supporting Information > Supporting File 2 > table S4): Whole-Genome Sequencing Pilot of the Central Asian Genomic Diversity Project Reveals Distinct Histories, Adaptation, and Introgression

1

4 Jul 2026, 17:05 UTC393 views3 reactionsread 6 August 2026
Forwarded from @PerkwanPhoto

Ancestry of a Late Neolithic Sample (I3931) from Aknashen, Armenia. ~65% Upper Mesopotamian PPNB ~19% CHG ~16% South Caspian N (ZNF + TTK) P = 0.45 Y-DNA: J-PF5174 (J2a1a1b1a1a) mtDNA: I1 Date: 5985-5836 calBCE @Perkwan

3

3 Jul 2026, 12:57 UTC463 views4 reactionsread 6 August 2026
Photo

🧬 qpAdm Model for Göktürk Samples from Özdemir et al. 2026 Study | (15 Samples) 60.2% Altai-Steppe_Huns 30.2% BulanKoby_Scythians 9.67% Medieval Sogdians Sample ID - Y-DNA - mtDNA: ALTGC075W - J2a-PF5050 - D2b1 ALTGC081W - J2a-L581 - F1b1b ALTGC082W - J2a-PH1795 - D4b2b ALTGC087W - J2a-L581 - F1b1b ALTGC088W - N/A (Female) - F1b1b ALTGC098W - J2a-L581 - D4j11 ALTS083W - J2a-PF5008 - H3h ALTS084W - N/A (Female) - F

4

2 Jul 2026, 21:12 UTC281 views6 reactionsread 6 August 2026
Forwarded from @vahaduoPhoto

Y-DNA Distribution of Native Americans From USA Q 589 R1 687 C2 66 I 192 J 62 G 23 H 1 E 181 L 2 B 4 A 4 N 4 O 12 T 3 Source: FTDNA

😁3👍2🔥1

30 Jun 2026, 12:24 UTC333 views5 reactionsread 6 August 2026
Forwarded from @EurasiadnaPhoto

Genetic Map for Central Asian Bronze Age Ancestry Генетическая карта наследия бронзового века Центральной Азии https://t.me/Eurasiadna

4👍1

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“Sapphire” (@sapphiregnm), 507 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/sapphiregnm.

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.