Channel
@morrisonurena
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
6,631subscribers
-63 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001384392158 |
|---|---|
| Type | Channel |
| Username | @morrisonurena |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/morrisonurena |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 14:49 | 6,631 | -17 |
| 18 Aug 2026, 22:57 | 6,648 | -16 |
| 15 Aug 2026, 20:28 | 6,664 | -12 |
| 12 Aug 2026, 13:06 | 6,676 | -6 |
| 9 Aug 2026, 15:31 | 6,682 | -12 |
| 6 Aug 2026, 17:00 | 6,694 | no change |
| 6 Aug 2026, 15:02 | 6,694 | first reading |
21 posts held, back to 28 June 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof 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 19 August 2026 |
|---|---|
| Posts held | 21 (28 June 2025 – 19 August 2026) |
| Views total | 698 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Aug 2026, 12:06 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.
Measured directly from 3 videos 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.
I couldn't sleep last night knowing that the DV-2027 program might not happen, so I filed a lawsuit with @redeaglelaw as plaintiff in San Diego about 3 am. Case number is: 26-cv-4738- JO-VET. The lawsuit has been assigned to US District Court Judge Jinsook Ohta. Link to complaint: https://drive.google.com/file/d/1hiPsPd0-plZUfbIQCnJSS3nLBYmGhZzP/view?usp=sharing Working on TRO now. -curtis🦅
FAQ: How many families have signed up to participate in REL’s 2nd group lawsuit to challenge the State Department’s 75-country pause on IV issuances? Answer: 102 families! Families are from Nepal, Thailand, Iran, Pakistan, Afghanistan, Ghana, Brazil, Egypt, Bangladesh, Colombia, DR Congo, Russia, Morocco, Belarus, Iraq, Nicaragua, Guatemala, Albania, Ethiopia, Jamaica, Bhutan, and Cameroon! Onboarding ends tonight …
I can report that we have 552 DV-2026 selectees have registered to participate in our class action group lawsuit! If you are a a DV-2026 selectee, and not a plaintiff in a lawsuit, it's not too late to participate. Onboarding ends in a little more than 14 hours! https://redeaglelaw.com/group-lawsuit-dv2026 -curtis🦅
📢 Announcement: Onboarding for Red Eagle Law's second DV-2026 group lawsuit is now open but ends on June 15, 2026! ⏳ To find out more, and register to participate, visit: https://redeaglelaw.com/group-lawsuit-dv2026
📢 We are offering a class action group lawsuit that is an opportunity for citizens of the 39 countries listed in Presidential Proclamations 10949 and 10998 to challenge the “hold” on the adjudication of USCIS benefits caused by PM-602-0192/4. ⏳Deadline to register: May 14, 2026 🗓Filing date for complaint: May 21, 2026 🔗Learn more & register: https://redeaglelaw.com/class-action-lawsuit 💬Questions? Join: https://t.me…
📣 PM-602-0192/4 Update! NYT has published a report on impacts of the holds on US healthcare! https://www.nytimes.com/2026/04/04/us/trumps-immigration-policy-sidelines-foreign-doctors-amid-shortage.html?unlocked_article_code=1.YVA.thgd._RZ-VTsK9WVh&smid=nytcore-ios-share Help us redistribute widely: https://x.com/redeaglelaw/status/2040482198852386835?s=46 https://www.facebook.com/redeaglelaw/posts/pfbid0bquwWDpxQS…
📣Update in litigation challenging PM-602-0192/94: We are now tracking 20 lawsuits challenging the lawfulness of USCIS's hold policy. (11 of those lawsuits are ours). Of the 3 orders issued: 2 PI granted 1 TRO denied. And still no class action. The fight continues! Onboarding for our last N-400 group lawsuit ends on March 13, 2026: https://redeaglelaw.com/group-lawsuit-n-400 -curtis
429 DV-2026 selectees from 70 countries have completed onboarding to partipate in our group lawsuit. (43 AOS/386 consular processing) And there are still 2 days left to participate! https://stopthedvpause.com/
Here are short excerpts from recent Q&A with Brit Simon - that address some of the most FAQ we continue to receive 📥
Update: 221 DV-2026 selectees have registered to participate from 43 different countries! - 191 are consular processing, and 20 are AOS). - Egypt (13) has passed Albania (12) - Azerbaijan (now 7) has passed 4 countries to now be #8. 5 days left to onboard! https://stopthedvpause.com
Update: So far we have 37 DV-2026 selectees (and their families) who have registered to participate from 23 different countries! Countries with 3 or more registrations: 1) Russian 2) Iran 3) Egypt 4) Turkey 5) Ukraine 6) Kyrgyzstan https://stopthedvpause.com/
Case prospectus for a group lawsuit challenging the State Department’s 75-Country IV issuance pause is live, onboarding begins soon! https://redeaglelaw.com/75-country-pause-lawsuit
Showing the 12 most recent of 21 posts we hold for @morrisonurena. 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 — 507,083 of 1,584,420entries 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Morrison Urena, LC” (@morrisonurena), 6,631 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/morrisonurena.
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.