KJDX

KJDX (93.3 FM, "JDX") is a radio station broadcasting a country music format. Licensed to the city of Susanville, Lassen County, Northeastern California. It serves portions of the northern Sierra Nevada region.

KJDX
CitySusanville, California
Broadcast areaSierra, Nevada
Frequency93.3 MHz
Branding"JDX"
SloganThe Sierras Best Country
Programming
FormatCountry music
AffiliationsABC Radio , Jones Radio Network
Ownership
OwnerSierra Broadcasting
(Sierra Broadcasting Corporation)
Sister stationsKSUE
History
First air date1983
Former call signsKNXN (1983-1988)
KQNC (1988-1997)
KHJQ (1997-2008)
Former frequencies102.1 MHz, 92.3 MHz
Technical information
Facility ID50306
ClassC0
ERP100,000 watts
HAAT352.0 meters
Transmitter coordinates40°27′13″N 120°34′14″W
Links
WebsiteKJDX

It first began broadcasting in 1983 under the call sign KNXN. The station is currently owned by Sierra Broadcasting.

History

The station was first assigned the call sign "KNXN" on May 23, 1983 on 102.1 FM. On May 27, 1988, the calls sign was changed to "KQNC". On February 20, 1997, the call sign was changed to KHJQ with a Hot AC format as "Q92". In 2003, the station moved to 92.3 FM.

In the summer of 2008, the station was moved to the recently vacated 93.3 FM frequency. On November 11, 2008, Sierra Broadcasting swapped call signs and formats between KJDX, which had vacated the 93.3 FM frequency in Susanville for the same frequency in Pollock Pines, California (in suburban Sacramento), and KHJQ.

This move brought KJDX back to the 93.3 FM frequency in Susanville. The newly moved KHJQ became KHLX, and is operated in Sacramento by Clear Channel.

gollark: You should, if you care, probably at least run it through an obufscator for .NET.
gollark: > 5. .net platform is cracker / hacker friendly Any program running on the client can INEVITABLY be reverse-engineered. Do not rely on it not experiencing that, because you will fail.
gollark: > 4. XAML - the incredibly messy UI technologyPerhaps, but this is not a *language* thing.
gollark: > 3. Garbage collector and memory leak detection tools?Again, not sure if anyone actually runs into this sort of issue in practice.
gollark: > 1. Performance penalties.> [some rambling about C++].NET is generally pretty much *fast enough*. If your application somehow hits performance bottlenecks, rewrite the slow bits in native code, don't just immediately take a development speed hit.> 2. Need to interoperate with C++ / Native (Windows) API’sI don't know how often you actually need to bind to a native API not wrapped by .NET or a third-party library, but you can do it, it's just annoying - but probably less than using C++ for everything!
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.