Channel
@grammarpage
On this record: Growth · Engagement · Posts · Citations · Cite this entry
916subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001308175257 |
|---|---|
| Type | Channel |
| Username | @grammarpage |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/grammarpage |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 20:08 | 916 | -4 |
| 6 Aug 2026, 14:05 | 920 | no change |
| 6 Aug 2026, 13:21 | 920 | -1 |
| 6 Aug 2026, 05:37 | 921 | first reading |
16 posts held, back to 24 April 2022 — 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 pageof 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 16 posts for this entry, the most recent from 30 September 2022. An engagement rate over an empty window would be a number about nothing.
Where did we come from? Why are we here? Where do we go when we die? What lies beyond And what lay before? Is anything certain in life? They say " Life is too short" "The here and the now" And " Youre only given one shot" But could there be more Have I lived before Or could this be all that weve got? If I die tomorrow Id be alright Because I believe That after were gone The spirit carries on I used to be frightene…
File, posted without a caption
Choose the best answers 1. Lisa eats ____ apple. ____ is delicious. a. an / She b. an / It c. the / They d. a / We 2. ____ brother is tall. ____ plays basketball. a. Our / She b. My / Our c. My / He d. His / She 3. John and ____ dad like desserts. ____ favorite dessert is chocolate cake. a. her / Her b. they / His c. his / Their d. their / Our 4. I like ____ sandals. ____ are cool! a. your / They b. my / It c. hi…
Sticker, posted without a caption
073. Thank you for… I. EXAMPLES: Thank you for what you have done for me. Thank you for your help. Thank you for the gift. Thank you for giving me a lift. Thank you for your advice. II. DIALOGUES: A: I have a big favor to ask. B: What is it? A: Well, I need to borrow $1,000 for the down payment on a car. B: OK, I’ll lend you the money but you have to pay it back as soon as you can. A: I promise I will. Thanks a m…
File, posted without a caption
@grammarpage #motivation
Photo, posted without a caption
Whoever vs. Whomever Choosing whoever or whomever can be easy. Whomever is an object pronoun and works like the pronouns him, her, and them (Give the document to whomever in the department). Whoever is a subject pronoun and works like the pronouns he, she, and they (Whoever wrote this poem should win a prize). It all comes down to understanding how who functions. Who and whoever are subject pronouns. In sentences…
Video, posted without a caption
Video, posted without a caption
@grammarpage
Showing the 12 most recent of 16 posts we hold for @grammarpage. 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 — 277,405 of 1,160,990entries 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.
Named by 4 registered channels — 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“⚜️English House⚜️” (@grammarpage), 916 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/grammarpage.
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.