Telegram RegisterThe public register of Telegram
Telegram profile photo for The Dugout Injury & Lineup News

Channel

The Dugout Injury & Lineup News

@mlb_injury_lineup

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

371subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001972441703
TypeChannel
Username@mlb_injury_lineup
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/mlb_injury_lineup

Topic

Sports — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

369376372.57 August 2026 — 371 subscribers8 August 2026 — 371 subscribers15 August 2026 — 369 subscribers30 August 2026 — 376 subscribers9 September 2026 — 374 subscribers18 September 2026 — 371 subscribers3717 August 202618 September 2026
6 measurements spanning 41 days. 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 368–377 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 01:57371-3
9 Sept 2026, 11:38374-2
30 Aug 2026, 06:35376+7
15 Aug 2026, 09:38369-2
8 Aug 2026, 06:19371no change
7 Aug 2026, 16:35371first reading

Engagement

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

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.0%

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 1 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 1 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 7 August 2026 to 8 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

8 Aug 2026, 00:12 UTC36 viewsread 8 August 2026

❗️Game Alert:❗️ #Braves-#Yankees expected to start at 9:00pm ET on Friday.

8 Aug 2026, 00:02 UTC51 viewsread 8 August 2026

🚫 Noah Schultz leaves game Friday in 1st inning. #WhiteSox made two mound visits and were forced to remove Schultz.

8 Aug 2026, 00:02 UTC38 viewsread 8 August 2026

❗️Game Alert:❗️ #Mets-#Pirates has resumed play Friday./ad_text

7 Aug 2026, 23:41 UTC39 viewsread 8 August 2026

❗️Game Alert:❗️ #BlueJays-#Phillies expected to start at 8:35pm ET on Friday.

7 Aug 2026, 23:21 UTC610 viewsread 8 August 2026

❗️Game Alert:❗️ #Mets-#Pirates in a rain delay Friday.

7 Aug 2026, 23:11 UTC42 viewsread 8 August 2026

#Tigers 8/7 K. McGonigle 3B G. Torres 2B D. Dingler C R. Greene LF C. Keith DH S. Torkelson 1B M. Clark CF J. Báez SS Z. McKinstry RF K. Montero SP

7 Aug 2026, 23:11 UTC40 viewsread 8 August 2026

❗️Game Alert:❗️ #Reds-#Nationals expected to start at 7:45pm ET on Friday./ad_text

7 Aug 2026, 22:51 UTC39 viewsread 8 August 2026

#Rays 8/7 Y. Díaz DH J. Aranda 1B J. Caminero 3B L. Hicks C C. Simpson LF J. DeLuca CF V. Mesa Jr. RF R. Palacios 2B T. Walls SS D. Rasmussen SP

7 Aug 2026, 22:41 UTC35 viewsread 8 August 2026

#Astros 8/7 J. Peña SS Y. Alvarez DH I. Paredes 3B J. Altuve 2B C. Walker 1B D. Varsho LF Y. Diaz C C. Smith RF J. Meyers CF R. Blanco SP

7 Aug 2026, 22:41 UTC37 viewsread 8 August 2026

🚫 Matt Chapman (core, hernia) expected to undergo season-ending surgery.

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

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.

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

“The Dugout Injury & Lineup News” (@mlb_injury_lineup), 371 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/mlb_injury_lineup.

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.