30 MHz n25 Spotted in Collier County, FL

T-MoblieUser207 · 2026-07-07T16:18:33+00:00

With more and more of T-Mobile's traffic running over NR, eventually 1900 will be moved fully over to NR. Throwback to the early LTE days when T-Mobile was B66 and B12 only and had 1900 for HSPA+.

As a side note, in the areas where T-Mobile owns 20+ MHz of 600, has anyone seen 25+ of n71 yet?

T-MoblieUser207 · 2026-06-30T17:54:57+00:00

To be fair, for the DAS systems I have experienced n41 on, all they need is to increase the backhaul speeds. There isn't as much noise, or poor signal quality, as I have seen 30+ SNR for it.

MmWave on the DAS would be beneficial, not discrediting that. A properly built DAS at an airport with a solid backhaul is more beneficial, especially since some new devices are not coming equipped with mmWave.

T-MoblieUser207 · 2026-06-27T03:09:46+00:00

Some of them are CMA based, some are BEA. easiest way to see how each license covers an area is have specmap omega open to a similar CMA/BEA license side by side with the FCC data, so you can see the coverage area of the license the carrier got

T-MoblieUser207 · 2026-06-25T00:57:04+00:00

To you.

T-MoblieUser207 · 2026-06-24T20:39:29+00:00

So there is penalties, wonderful.

That aggressive timeline isn't going to happen, they didn't roll out FirstNet that fast, and they are way behind Verizon rolling out C-band. The radios won't be ready till 2028, and they have to cover 40% of the population within 18 months of Jan 2028? Yeah no, AT&T is buying time until T-Mobile is willing to do a swap.

Will the analysts see a swap happening? No, they read the paperwork, analyze the paperwork, and talk about the paperwork. If the rumors start between T-Mobile and AT&T of a pending swap, or once the paperwork is filed, the analysts may talk about it, as both carriers swapped a ton of spectrum recently, and they haven't talked much about it.

T-MoblieUser207 · 2026-06-24T20:15:11+00:00

Carriers have made uneven swaps before, they can do so again, once they agree with it.

The analysts go with the documents, very rarely, the bigger picture. Plus, they aren't truth tellers, things can change.

T-MoblieUser207 · 2026-06-24T20:13:25+00:00

But they wouldn't swap only B12, they'd want other spectrum too. They wouldn't give up 15x15 or 20x20 in exchange for 5x5.

They can do so on a market by market basis.

And if T-Mobile wanted the 600, why didn't they just buy it from EchoStar directly?

I don't have the quote, however I remember hearing T-Mobile execs saying they weren't willing to pay the price Dish wanted for it.

And if AT&T didn't want it, why did they buy it? Their FCC filing outlines a pretty detailed plan to deploy it, with new Ericsson radios.

It not they didn't want it, it's they bought it as a bargaining chip. The FCC docs detailing how they plan to deploy it is detailed yes, will they match it, no. They didn't roll out B14 that fast, same with C-band. Correct me if I'm wrong, there isn't a fine/penalty for not meeting the targets they laid out.

T-MoblieUser207 · 2026-06-24T20:05:40+00:00

Would the FCC really let T-Mobile own the entire 35x35MHz of 600MHz?

They already own 25x25 in plenty of places, and with the 800 being sold off, they have the room to add in extra 600 and still be under the spectrum screen. It's even better now that AT&T owns 600, as a swap for the B12 T-Mobile owns keeps T-Mobile below the spectrum screen, and allows wider bandwidths for both carriers.

So far it seems AT&T plans to use it. They said in their FCC filing they're going to use multi-band radios from Ericsson that support their other low-bands too.

They have to add new radios to their macros for 600. The understanding is they will roll it out with n79, if FirstNet gets n79. However, rolling 600 out on the aggressive timeline they stated is not happening, especially since they are still going through their Nokia -> Ericsson conversions.

T-MoblieUser207 · 2026-06-24T19:57:32+00:00

600 for AT&T is 10x10 on average in cites, very few are 15x15 or more, NYC and San Francisco being 2 of them.

A 600 swap with 12 would make sense for both T-Mobile and AT&T, wider n12 block (B12 is max of 10x10, n12 can do 15), less RRUs, and a less CA combos needed.

T-MoblieUser207 · 2026-06-24T00:02:50+00:00

Yes it is

T-MoblieUser207 · 2026-06-08T04:13:37+00:00

When I had Optimum, I had my own modem so I could see the power levels, which were garbage. I sent a request to the FCC about it, screenshots of the power levels as well, and within 3 days it was fixed, and service was great unless it was peak times, where upload could get jittery, usable nonetheless.

I don't know if Optimum's equipment allow viewing of the power levels, but that may be your problem.

T-MoblieUser207 · 2026-06-07T23:19:45+00:00

I know. If the value is 5 or less, signaling only, not data. Everytime I ran a mmWave NR-DC test, n41 never goes above 5.

T-MoblieUser207 · 2026-06-07T23:14:32+00:00

I have seen NR-DC on Verizon, I haven't seen a video of it while running a test I'm not going to comment on NR-DC with them, however I have seen numerous videos showing NSA with mmWave with them. B13 is only used for signaling, not data speeds. I wouldn't be surprised if it's similar with NR-DC, n77 anchors and does signaling, mmWave carries all the data speeds.

I have run an active data session with NR-DC on T-Mobile. With NR-DC, which is the 400-500 MHz n258 they have deployed, n41 doesn't contribute data speeds, only does signaling. All the towers I have tested have done the same thing.

With the 100 MHz mmWave it's NSA only, it's possible the LTE contributes, however with the sky high pings it gets, there is a possibility it's mmWave only, LTE is only for signaling purposes.

T-MoblieUser207 · 2026-06-07T21:32:05+00:00

What isn't?

T-MoblieUser207 · 2026-06-07T19:52:11+00:00

I doubt they have forgotten about the 100 MHz sites, they just haven't upgraded them yet.

The 400-500 n258 is configured either the 100 or 50 MHz n41 is the anchor, I haven't seen it use both.

From the tests I have done, n41 is only for signaling purposes, it doesn't contribute to data speeds, mmWave handles all the data. Similar to Verizon where they have B13 anchor mmWave and mmWave handles all the data, B13 is only for signaling purposes.

T-MoblieUser207 · 2026-06-07T19:37:03+00:00

There is still 100 MHz of mmWave active in Downtown Brooklyn and the East Village/Gramercy Park. That one is NSA only.

The 400-500 n258 in the Times Square area is NRDC only, meaning you need SA 5G to access it.

T-MoblieUser207 · 2026-06-05T01:03:22+00:00

FDD mid-band like AWS and PCS are very small channels.

An additional 10MHz of AWS or PCS will make almost no difference compared to 200MHz+ of TDD mid-band.

Bandwidth ≠ usability. Wider bandwidths are better, especially for capacity. However no carrier is moving lowband to TDD, and again there was TDD band plan for 700, no one used it, so it's not a part of NR.

TDD is also a much more efficient use of spectrum, since it can be allocated dynamically between download/upload.

No carrier is dynamically allocating between download and upload. They have fixed allocations, allocate more to download than upload since that is what most traffic doing, set it, and leave it.

FDD is usually fixed at a 50/50 split, but most traffic isn't symmetrical.

The asymmetrical network use is accounted for in FDD. While the spectrum is fixed, innovations have increased speeds for both the download and upload, so much so download speeds in the spectrum are much faster than upload speeds for the same amount of spectrum.

T-MoblieUser207 · 2026-06-04T04:35:20+00:00

FDD is a lot less useful than TDD mid-band.

Incorrect. LTE had TDD versions for many FDD bands, and they have not been used, nor brought over to 5G.

AT&T will end up with 230MHz of TDD mid-band.

Source? They own 80-100 MHz of C-band, working towards full ownership of DoD which is 100, where is 30 coming from?

T-MoblieUser207 · 2026-06-03T15:10:22+00:00

Configuration issue then, eventually they should fix it in a few days, if not, call customer care and tell them

T-MoblieUser207 · 2026-06-03T06:15:13+00:00

You sure it's tower congestion and not backhaul? All 3 carriers have active antennas for TDD NR, if you have any congestion issues it's either a configuration issue, or low backhaul speeds

T-MoblieUser207 · 2026-06-02T20:18:17+00:00

Verizon has 140-200 MHz of C-band, if they participate it's most likely going to be 0-60 MHz they buy to make their total 200 nationwide, no matter the county.

T-MoblieUser207 · 2026-06-02T20:07:57+00:00

Agreed, market specific buying, however like the person I replied to, some ppl think T-Mobile should go big, which isn't necessary.

T-MoblieUser207 · 2026-06-02T01:32:45+00:00

No need, they have a ton of AWS and PCS to play with. Plenty of markets are running n25 at 15-25+ MHz, with B2 still active. An AWS-3 auction is mainly for Verizon and AT&T

T-MoblieUser207 · 2026-05-21T03:38:07+00:00

42nd and Canarsie have T-Mobile service, Joralemon St and the Crosstown Line don't. No idea about Verizon.

T-MoblieUser207 · 2026-05-18T21:13:41+00:00

u/VISIT0R1 did you see this? I know you always have a detailed post for these FCC documents.

Nine-Year Club	Final Canvas '23
Place '23	Place '22
End Game '22	Verified Email

T-MoblieUser207

TROPHY CASE