Telegram RegisterThe public register of Telegram
Telegram profile photo for OʀᴛʜᴏRᴇᴀD

Channel

OʀᴛʜᴏRᴇᴀD

@OrthoReaD

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

1,467subscribers

+1 since we began measuring on 2 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003614560993
TypeChannel
Username@OrthoReaD
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live4 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/OrthoReaD

Growth

1,4661,4671,466.52 Sept 2026, 19:46 — 1,466 subscribers2 Sept 2026, 20:00 — 1,466 subscribers4 Sept 2026, 01:20 — 1,467 subscribers2 Sept 2026, 19:464 Sept 2026, 01:20
3 measurements spanning 1 day, net +1. 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 1,466–1,467 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 01:201,467+1
2 Sept 2026, 20:001,466no change
2 Sept 2026, 19:461,466first reading

Engagement

20 posts held, back to 4 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.

ERR · 30 days
18.5%
avg views ÷ 1,467 subscribers
Avg views / post
271
2 posts measured
Reaction rate
3.47%
reactions ÷ views · ER floor
Posts in window
2
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 August 2026
Posts held20 (4 June 202615 August 2026)
Views total542
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 20:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
650.0%
👍541.7%
🙏18.33%

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

Measured over the 20 most recent posts we hold, published 4 June 2026 to 15 August 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

15 Aug 2026, 16:59 UTC173 views6 reactionsread 2 September 2026
Forwarded from @OrthoPoLLsPhoto

Campbell's MCQs are coming very soon https://t.me/OrthoPoLLs/10650

👍41🙏1

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

8 Aug 2026, 13:40 UTC369 viewsread 2 September 2026
Forwarded from @OrthoFileSPhoto

https://t.me/OrthoFileS/2482

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

28 Jul 2026, 20:41 UTC463 views2 reactionsread 2 September 2026
Forwarded from @OrthoPoLLs

📗 Concise Orthopaedic Notes 📋 First Poll of Each Chapter — Quick Navigation Index 💾 Save this message to track your progress & revisit any chapter! ━━━━━━━━━━━━━━━━━━━━━ 📖 Chapter 1 — General Guidance for Exams 🔗 https://t.me/OrthoPoLLs/9925 🧬 Chapter 2 — Orthopaedic Basic Sciences 🔗 https://t.me/OrthoPoLLs/9937 🦴 Chapter 3 — Orthopaedic Adult Pathology 🔗 https://t.me/OrthoPoLLs/9958 👶 Chapter 4 — Paediatric Or

1👍1

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

26 Jul 2026, 09:12 UTC428 views1 reactionsread 2 September 2026
Forwarded from @OrthoPoLLs

📘 Miller's Review of Orthopaedics 📋 First Poll of Each Set — Quick Navigation Index 💾 Save this message to track your progress & revisit any set! ━━━━━━━━━━━━━━━━━━━━━ 🔹 Set 1 → https://t.me/OrthoPoLLs/8597 🔹 Set 2 → https://t.me/OrthoPoLLs/8616 🔹 Set 3 → https://t.me/OrthoPoLLs/8638 🔹 Set 4 → https://t.me/OrthoPoLLs/8649 🔹 Set 5 → https://t.me/OrthoPoLLs/8661 🔹 Set 6 → https://t.me/OrthoPoLLs/8672 🔹 Set 7 → https

1

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

10 Jul 2026, 15:39 UTC483 views1 reactionsread 2 September 2026
Forwarded from @OrthoPoLLs

📘 Apley's System of Orthopaedics & Fractures 📋 First Poll of Each Chapter — Quick Navigation Index 💾 Save this message to track your progress & revisit any chapter! ━━━━━━━━━━━━━━━━━━━━━ 📗 PART 1 — GENERAL ORTHOPAEDICS ━━━━━━━━━━━━━━━━━━━━━ 🦴 Chapter 1 — Diagnosis in Orthopaedics 🔗 https://t.me/OrthoPoLLs/8119 🦠 Chapter 2 — Infection 🔗 https://t.me/OrthoPoLLs/8130 🔥 Chapter 3 — Inflammatory Rheumatic Disorders 🔗

1

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

3 Jul 2026, 15:41 UTC509 viewsread 2 September 2026
Forwarded from @OrthoPoLLs

Dear Orthos, Enhance your clinical foundation and test your orthopedic knowledge with our latest interactive review series. 📚🦴 We are launching a comprehensive, chapter-by-chapter review of Apley's System of Orthopedics. To help you solidify key concepts and evaluate your understanding, we have designed a specialized 10-poll set for each chapter. 📝📊 Assess your grasp of essential orthopedic principles and track yo

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

8 Jun 2026, 17:10 UTC≈1,050 views1 reactionsread 2 September 2026

​❓ OrthoReaD Mystery Case 1 (The Gadolinium Trap) ​The Scenario: A patient presents 2 years after an L4-L5 microdiscectomy with a sudden recurrence of severe, unilateral radicular leg pain. An unenhanced MRI reveals a soft tissue mass in the anterior epidural space, effacing the traversing nerve root. ​A junior resident is eager to book the patient for an urgent revision decompression, assuming it is a recurrent disc

1

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

8 Jun 2026, 09:10 UTC767 viewsread 2 September 2026

​❓ OrthoReaD Mystery Case 1 (The Biomechanical Contraindication) ​The Scenario: A 42-year-old patient presents with chronic, severe discogenic back pain at L4-L5. The disc is heavily degenerated, and there is no instability or spondylolisthesis. A fellow suggests a Total Disc Replacement (TDR) to preserve motion and prevent adjacent segment disease. However, the preoperative CT scan reveals moderate-to-severe hypertr

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

8 Jun 2026, 09:02 UTC529 views1 reactionsread 2 September 2026
Photo

Chapter 32

1

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

7 Jun 2026, 13:10 UTC569 viewsread 2 September 2026

​❓ OrthoReaD Mystery Case 1 (The Avascular Corridor) ​The Scenario: A fellow is setting up for a Minimally Invasive Transforaminal Lumbar Interbody Fusion (MIS TLIF). Instead of stripping the paraspinal muscles off the spinous processes (which causes denervation and atrophy), he uses serial dilators to gently separate the muscle fibers and dock his tubular retractor directly over the facet joint. ​The senior attendin

Signed Sᴀʟᴀᴍ Aʙᴀʏᴀᴄʜɪ

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

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.

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.

Names

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

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

“OʀᴛʜᴏRᴇᴀD” (@OrthoReaD), 1,467 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/OrthoReaD.

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.