BIZTRAC BETA
Site preparation

JOHN GALTEN AS

Org. no. 983792324 Limited company (AS) Åmot Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 153.5m
Operating profit NOK 33.3m
Equity NOK 106.5m
Incorporated 2001
Employees 49
Share capital NOK 3.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JOHN GALTEN AS is registered as a limited company in Åmot, Innlandet with organisation number 983792324. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2001 and has 49 registered employees. Registered share capital is NOK 3.5m, divided into 3450 shares. The company's stated purpose is: “Drift av entreprenørforretning samt ved aksjetegning eller på annen måte gjøre seg interessert i foretagender innen bransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 153.5m in revenue and NOK 33.3m in operating profit.

Key figures · 2024

Revenue
NOK 153.5m
Operating profit
NOK 33.3m
Equity
NOK 106.5m
Est. value
NOK 154.5m

Financial health · 2024

Liquidity
2.04
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
58.0%
Very good
Equity as a share of total capital

Who owns JOHN GALTEN AS?

MYHRE ANLEGG AS
JOHN GALTEN AS
NOK 153.5m rev. · NOK 33.3m profit

JOHN GALTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOHN GALTEN AS

Who owns JOHN GALTEN AS?

MYHRE ANLEGG AS is the largest registered owner, with 100.0%.

What is the revenue of JOHN GALTEN AS?

JOHN GALTEN AS had revenue of NOK 153.5m in 2024.

Who is the general manager of JOHN GALTEN AS?

Frank Myhre is registered as general manager of JOHN GALTEN AS.

Where is JOHN GALTEN AS based?

JOHN GALTEN AS has its business address in Rena.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.