Channel
@nhlibertyforum
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
32subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001668273079 |
|---|---|
| Type | Channel |
| Username | @nhlibertyforum |
| Description | NH Liberty Forum 25 NHLibertyForum.com |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/nhlibertyforum |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 02:02 | 32 | no change |
| 7 Aug 2026, 22:37 | 32 | first reading |
20 posts held, back to 4 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 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 20 posts for this entry, the most recent from 6 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
March 6, 2026 at 03:14PM RT @AFP_NH: Great time at @NHLibertyForum speaking with Granite Staters who are passionate about keeping New Hampshire free! https://t.co/z… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
March 6, 2026 at 03:14PM RT @DCNHtv: New Hampshire Liberty Forum LIVE@NHLibertyForumThursday, March 5 – Sunday, March 8, 2026Concord, NHhttps://t.co/nOb1Rx97mk 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
2026-02-24T02:22:44+00:00 RT @IanHuyett: Looking forward to speaking at @NHLibertyForum on how New Hampshire can become a leading hub of biotech innovation by passin… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
February 20, 2026 at 10:27AM RT @FreeStateNH: 🚨 BIG ANNOUNCEMENT! 🚨We're thrilled to reveal that @ThomasEWoods will be our VIP Dinner Keynote Speaker at the 2026 New… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
January 20, 2026 at 01:04PM RT @FreeStateNH: "Build Freedom at the State House."NH HOUSE MAJORITY LEADER JASON OSBORNE TO SPEAK AT THE 2026 NH LIBERTY FORUM!As one… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
January 17, 2026 at 06:41PM Got tickets?https://t.co/dkdbOX5yUg https://t.co/uZdXiNzmbc 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
January 12, 2026 at 09:33AM RT @FreeStateNH: Interested in being part of NH Liberty Forum’s Media Room? We want to hear from you! https://t.co/siJYLfm8rd https://t.co/… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
November 28, 2025 at 03:12PM RT @FreeStateNH: "This is the week to count our blessings — and there are so many here in New Hampshire."Today's newsletter by FSP Direct… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
November 28, 2025 at 01:30PM RT @FreeStateNH: BUILD FREEDOM!Next March 5-8, we look forward to hosting Jay Noone at the 2026 NH Liberty Forum.Jay will present and f… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
November 21, 2025 at 01:36PM RT @FreeStateNH: 2026 NH LIBERTY FORUM ANNOUNCEMENT:We are excited to announce our first confirmed presenter for next year's "Liberty In… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
November 20, 2025 at 01:16PM RT @FreeStateNH: 2026 NH LIBERTY FORUM ANNOUNCEMENT!We are pleased to announce our first Main Stage speaker:@BobMurphyEcon — an econom… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
June 12, 2025 at 09:14PM RT @FreeStateNH: @DennisPrattFree @EricBrakey Javier Milei and the Liberty-For-Real Lessons of Argentina with Skot Shellerhttps://t.co/pB… 🔗Source: 𝕏 @NHLibertyForum 🎟 Tickets: NHLibertyForum.com 📣 Telegram: @NHLibertyForum
Signed IFTTT
Showing the 12 most recent of 20 posts we hold for @nhlibertyforum. 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 — 1,218,732 of 1,481,346entries 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 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.
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.
@nhlibertyforum named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“NH Liberty Forum” (@nhlibertyforum), 32 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/nhlibertyforum.
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.