Team lane//PO load GA»AZ//CA»GA $10500 per round trip ($2.4rpm) Can do 1.5 RT or 2RT. Gross gonna be 15k-20k FOR DM https://t.me/Ben_dispatch11

Channel
DEDICATED LANE'S & TRUCK DRIVER'S
@BEN_HIRING
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
40subscribers
+1 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 | -1003196801807 |
|---|---|
| Type | Channel |
| Username | @BEN_HIRING |
| Created | Between 1 September 2025 and 17 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 8 October 2026 |
| On Telegram | t.me/BEN_HIRING |
Topic
Job listings — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 07:38 | 40 | +2 |
| 12 Sept 2026, 15:18 | 38 | -1 |
| 10 Aug 2026, 20:30 | 39 | no change |
| 7 Aug 2026, 18:23 | 39 | first reading |
Engagement
20 posts held, back to 17 November 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 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 15 May 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 2 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 17 November 2025 to 15 May 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
USPS lane 4 round trip Per load $2500 FOR DM https://t.me/Ben_dispatch11
AMAZON TEAM LANE ACTIVE ROUTE 🔥🔥
🚛 Driver: Owner Operators 🗺 Route: Phoenix, AZ → Davenport, FL • Gross: $17 500+ (weekly) • Per Mile: $2.20+ • Round Trip: Hook&Drop and live/live back 📍 Route: ➡️Phoenix, AZ > Davenport, FL 💰 $$7,510 (Amazon) - Hook/Drop ⬅️FL - GA - AL > Phoenix, AZ 💰 $2.500 - $3.000 (Spot / Street Loads - Live/Live 1. Stable, Year-Round Freight 2. Weekly On time Payment 3. Free & Fast Online Hiring Process You can text to get …
🚛 Driver: Owner Operators 🗺 Route: Hazelwood, MO → Phillipsburg, NJ → Aurora, IL → Hazelwood, MO • Gross: $12 500+ (weekly) • Per Mile: $2.15+ • Round Trip: Live/Live 1. Stable, Year-Round Freight 2. Weekly On time Payment 3. Free & Fast Online Hiring Process You can text to get more information : https://t.me/Ben_Recruiter
🚛 Driver: Owner Operators 🗺 Route: Hazelwood, MO → Palmetto, GA → Montgomery, AL → Birmingham, AL → Olathe, KS → Hazelwood, MO • Gross: $12 000+ (weekly) • Net Profit: $7 000+ • Round Trip: Live/Live 1. Stable, Year-Round Freight 2. Weekly On time Payment 3. Free & Fast Online Hiring Process You can text to get more information : https://t.me/Ben_Recruiter
USPS Power only round trip Lane Loaded pick up empty back 495 miles pays 1100 Tuesday to Sunday Gross 8000$ fuel:1250 Tolls : no Disp fee: 960 Insurance: 575 Net: 4500-4800$ You can text to get more information : https://t.me/Ben_Recruiter
Need driver's to amazon spot Performance A+ REQUIREMENTS 2 year's experience 🔥🔥🔥🔥 You can text to get more information : https://t.me/Ben_Recruiter
🚚 Driver: Owner Operators 🗺 Route: Northampton, PA → Kansas City, MO → Northampton, PA • Gross: $8 600+ (weekly) • Net Profit: $4 500+ • Round Trip: Hook&Live 1. Stable, Year-Round Freight 2. Weekly On time Payment 3. Free & Fast Online Hiring Process You can text to get more information : https://t.me/Ben_Recruiter
❤1
Video, posted without a caption
ANY WORD'S GUY'S 👀
Laredo TX loads Laredo to Mechanicsburg PA 1764 mile $3800 24/7 both side Laredo to Windom MN 1298 mile $3200 24/7 both sides Laredo to Abingdon VA with appt but straight 1363 mile $3100 Laredo to Whitestown IN 1338 mile $2900 24/7 both Laredo to Statesville NC 1386 mile $2900 24/7 both Laredo to Altoona IA 1175 mile $2600 24/7 Laredo to Cleveland NC 1400 mile $3000 24/7 both Laredo to SC 1370 miles $3000 Lare…
Showing the 12 most recent of 20 posts we hold for @BEN_HIRING. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@BEN_HIRING named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 5 posts, 11 August 2026 – 11 August 2026
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“DEDICATED LANE'S & TRUCK DRIVER'S” (@BEN_HIRING), 40 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/BEN_HIRING.
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.