TGP Coordinate Conversion on NTTR vs Caucasus

I am trying to understand the Harrier's TGP coordinates. Is it displayed in Decimal Degrees or DMS? If I try to treat it like decimal degrees, and look the location up on Google, it is way off. So assuming it outputs in DMS:

On Caucasus, here is some coordinates at Sochi along with Google Maps.

N4326350

E03955461

Adding spaces and a decimal to the last digit:

N43 26 35.0

E039 55 46.1

Here are those coordinates now, which when plugged into Google Maps gives us a close match.

43°26'35.0"N 039°55'46.1"E

https://www.google.com/maps/place/43%C2%B026'35.0%22N+39%C2%B055'46.1%22E/@43.4425524,39.9307572,1577m/data=!3m1!1e3!4m5!3m4!1s0x0:0x0!8m2!3d43.4430556!4d39.9294722

-----------------------------------------------------------------------------------------

Okay, now. Same method on NTTR, but I get coordinates that don't quite work.

Here is Creech AFB:

Here is the output:

N3635033

W-11580892

N36 35 03.3

W-115 80 89.2

As far as I understand, on the longitude, the minutes and seconds can't be over 60. So why is the TGP outputting this?

Google Maps won't accept this:

36°35'03.3"N 115°80'89.2"W

That intersection, according to Google Maps is about: 36°35'03.1"N 115°40'55.6"W

I'm away from my rig, so I can't test it, myself. Could you fly over or park at Creech and see if the INS gives you the same issue? Also, if you have another plane with a targeting pod, check what it indicates on the same intersection. It could be the Nevada map.

It'd be splendid if the pod just talked the same language as the Harrier's own nav system regarding coords.