4gTurbo Is Coming To Verizon & T-Mobile But Neither Owns The Bang On Domains 4gTurbo.com Or Turbo4g.com

2011 November 19
by Michael H. Berkens

According to some recent registrations by Mark Monitor it seems a product known as 4gTurbo is coming to at least two carriers, AT&T and T-Mobile.

Some recent domain name registrations include:

4gturbo.info

4gturbo.net

4gturbo.org

tmobile4gturbo.com

t-mobile4gturbo.com

tmobile4gturbo.info

tmobile4gturbo.net

t-mobile4gturbo.info

4gTurbo.com is owned by a company in Boca Raton and goes to a parked page.

Turbo4g.com is owned by someone in Sweden and registered in 2009. It current goes to a Godaddy.com placeholder.

It looks like Verizon is planning on rolling out a service call 4gTurbo which will be faster than its 4g LTE product.

Both T-Mobile and AT&T are advertising on Google PPC under the term 4G Turbo although I can’t find anything that AT&T is planning on rolling out this service.

7 Responses leave one →
  1. 2011 November 19
    Ron permalink

    Would this be an example of a pigeon sh*t domain that actually pays off?

  2. 2011 November 19
    Max permalink

    they also havn`t:

    4-gturbo.com
    turbo4-g.com

  3. 2011 November 20
    domains permalink

    LOL

    5gturbo
    6gturbo

    Registered. Only in domaining

    7gTurbo not taken yet. Hurry grab it. LOL.

  4. 2011 November 20

    But Neither Owns … 4gTurbo.com Or Turbo4g.com

    wrong move … now that they have revealed their interest in this name their prices should increase very much :)

  5. 2011 November 20
    Alan permalink

    Surprisingly, I don’t think they will try and purchase the names. Many companies will only use
    a name with their brand included

  6. 2011 November 21

    So they have registered domain names in three extensions…
    Cool.

  7. 2011 November 21

    The domain names are gonna sky-rocket with their price, great move buying them 2 years ago.

Leave a Reply

Note: You can use basic XHTML in your comments. Your email address will never be published.

Subscribe to this comment feed via RSS

Please copy the string W1bvkS to the field below: