Channel
@mgcp_1
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry
35subscribers
+24 since we began measuring on 15 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004485043617 |
|---|---|
| Type | Channel |
| Username | @mgcp_1 |
| Created | 5 September 2026 — measured — dated from the channel’s first post |
| First recorded | 15 October 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/mgcp_1 |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 30 October 2026 and assigned it the closest of 31 fixed categories, at 94% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 8 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @Clinical_Notes/549131 Aug 2026, 19:03 UTC | @mgcp_1/2 · this entry5 Sept 2026, 14:38 UTC | 1.00 | 5 days |
| @Clinical_Notes/54973 Sept 2026, 16:35 UTC | @mgcp_1/3 · this entry5 Sept 2026, 14:38 UTC | 1.00 | 46 hours |
| @Clinical_Notes/55004 Sept 2026, 16:46 UTC | @mgcp_1/5 · this entry5 Sept 2026, 14:38 UTC | 1.00 | 22 hours |
| @mgcp_1/7 · this entry6 Sept 2026, 15:28 UTC | @Clinical_Notes/55026 Sept 2026, 16:28 UTC | 1.00 | 60 minutes |
| @mgcp_1/8 · this entry6 Sept 2026, 17:16 UTC | @Clinical_Notes/55036 Sept 2026, 17:19 UTC | 1.00 | 3 minutes |
| @mgcp_1/10 · this entry6 Oct 2026, 17:37 UTC | @Clinical_Notes/55786 Oct 2026, 17:47 UTC | 1.00 | 10 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Clinical_Notes | 11 (8/8 hand-verifiable sample passed) | 1.00 | 50 minutes | this entry (6–5) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 5 September 2026 to 14 October 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 8 channels, the one whose matching posts we hold earliest is @OmarAlsubari. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 8 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 06:46 | 35 | +3 |
| 30 Oct 2026, 20:01 | 32 | +17 |
| 22 Oct 2026, 20:50 | 15 | +4 |
| 15 Oct 2026, 05:22 | 11 | no change |
| 15 Oct 2026, 04:47 | 11 | first reading |
13 posts held, back to 5 September 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 page of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 14 October 2026 |
|---|---|
| Posts held | 13 (5 September 2026 – 14 October 2026) |
| Views total | 695 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Oct 2026, 05:22 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.
Telegram’s own ‘edited’ marker: 1 of 1 post held from the last 30 days (100.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
✅👇✅ كيف تنتقل من دراسة الأدوية إلى التفكير السريري المنظّم؟ دراسة الأدوية والعلاجيات تمنحك المعرفة، لكن تطبيق هذه المعرفة على مريض حقيقي يحتاج إلى منهج واضح يساعدك على تقييم الحالة، وتحليل العلاج، وتحديد المشكلات، وبناء خطة رعاية ومتابعة نتائجها. من هنا جاءت فكرة: MGCP — Masood Guide to Clinical Practice 📚 Pharmaceutical Care Practice From Theory to Practice | من النظرية إلى التطبيق العملي ليس مجرد كتاب لقراءة ال…
✅🆕🆕🆕🆕🆕🆕✅✅ كتاب الحالات لديبرو النسخه 2026 ع شكل ملفات Schwinghammer's Pharmacotherapy Casebook النسخه 13 الاخير #Clinical_Notes
File, posted without a caption
✅🆕🆕🆕 📚👇 MGCP — A First Look Inside هل يمكن أن يكون Clinical Pharmacy أكثر من مجرد معرفة الأدوية؟ هذا هو السؤال الذي انطلق منه MGCP — Masood Guide to Clinical Practice. كتاب عملي صُمم لطلاب الصيدلة السريرية والمتدربين لمساعدتهم على الانتقال من المعرفة النظرية إلى التفكير السريري والتطبيق العملي. ويأخذ القارئ في مسار متدرج يبدأ من Patient Assessment ويمر عبر Medication Reconciliation, DTP Identification, Prioriti…
✅❓🧸 هل لاحظت أن فصول MGCP ليست مرتبة عشوائيًا؟ 👇📖 الهدف لم يكن أن نضع أكبر قدر ممكن من المعلومات داخل كتاب واحد… بل أن يتحرك القارئ خطوة بخطوة مع طريقة التفكير السريري:🌟 Pharmaceutical Care ↓ Clinical Skills ↓ Patient Assessment ↓ Drug Therapy Problems ↓ Care Plan ↓ Implementation & Follow-up ↓ Documentation & Communication ↓ Evidence-Informed Care ↓ Clinical Monitoring ↓ Medication Safety يعني أنك لا تتعلم فقط: …
🌟🌟 Your Recommendation Means Nothing If It Isn't Heard. Clinical communication is a clinical intervention. أحيانًا المشكلة ليست أنك لم تعرف القرار الصحيح. المشكلة أنك لم تعرف كيف توصله. في Clinical Pharmacy، لا يكفي أن تقول: “The dose should be adjusted.” قل: What is the risk? What do you recommend? Why? What is the safer alternative? هذه ليست مجرد communication skills.🌟 هذه Clinical Intervention. لأن القرار السرير…
✅🔥 تتخذ القرار الصحيح سريريًا… ثم يضيع أثره.🌟 لأن Clinical Pharmacy ليست فقط: Identify → Plan → Intervene → Monitor هناك خطوة لا تقل أهمية: Document. ما المشكلة؟ What was the problem? ماذا فعلت؟ What was done? ولماذا؟ Why was it done? وماذا يجب أن يحدث بعد ذلك؟ What happens next? لأن القرار السريري الذي لا يصل بوضوح إلى الفريق قد لا يتحول إلى continuity of care. Good clinical reasoning deserves good documentation. —…
🆕🆕🆕✅✅ الصيدلي السريري لا ينسخ قائمة الأدوية… بل يحقق فيها.🌟 🔎 A clinical pharmacist does not simply copy a medication list… they investigate it. . 🔎🔎 قائمة الأدوية ليست دائمًا الحقيقة. A medication list is not always the truth. Ask what the patient actually takes. Verify the information. Look for discrepancies. Then decide what requires action. هذه هي عقلية الـ Clinical Pharmacist 👇 #MGCP | Pharmaceutical Care Prac…
📣✅✅ المشكلة في Clinical Pharmacy ليست دائمًا أنك لا تعرف الدواء… أحيانًا أنك لم تسأل السؤال الصحيح. قبل أن تفكر في تغيير العلاج، توقف واسأل: Is it indicated? Is it effective? Is it safe? Is the patient able to use it as intended? أربع أسئلة بسيطة قد تحوّل polypharmacy من قائمة أدوية معقدة إلى structured clinical reasoning. وهنا يبدأ الانتقال الحقيقي: From knowing drugs → to thinking clinically. #MGCP | Pharmaceutica…
✅✅🌟 بعد ما تكتشف الـDRP… لا تتسرع في تغيير الدواء. في Clinical Pharmacy، السؤال الأهم ليس: “What should I change?” بل: “What outcome am I trying to achieve?” بعدها تبدأ العملية الحقيقية: Options → Intervention → Monitoring → Follow-up 🌟 لأن identifying a problem is only the beginning. From identifying problems → to designing better outcomes. 👇 — #MGCP | Pharmaceutical Care Practice #Clinical_Notes
✅✅🌟✅ عملت الـclinical intervention… وماذا بعد؟ في Clinical Pharmacy، intervention🧸 🌟 ليست نهاية العملية. 🌟لازم تعرف: What will I monitor? When will I reassess? What will tell me that the plan worked — or failed?🌟 لأن: No monitoring = No real follow-up. و clinical reasoning لا يكتمل بالقرار فقط، بل عندما تتابع النتيجة وتغلق الحلقة. From intervention → to measurable outcomes. — #MGCP | Pharmaceutical Care Practice 👇 #C…
🆕🆕🆕🆕🆕🆕🆕🆕🆕 الصيدلة السريرية لا تُتعلم بالحفظ فقط… بل بالممارسة. قريبًا،🌟 كتاب صُمم ليأخذك حيث تبدأ الممارسة الحقيقية:📖 من النظرية… إلى المريض.🌟 من المعرفة… إلى القرار.🌟 من القرار… إلى الرعاية. MGCP 👇 Pharmaceutical Care Practice From Theory to Practice قريبًا. شيءٌ مختلف ينتظرك. #MGCP
Showing the 12 most recent of 13 posts we hold for @mgcp_1. 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.
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.
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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“MGCP” (@mgcp_1), 35 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/mgcp_1.
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.