BIZTRAC BETA
Site preparation

KYSTANLEGG AS

Org. no. 930637971 Limited company (AS) Rana Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 873,000
Equity NOK 1.1m
Incorporated 2022
Share capital NOK 150,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-03-17 Aksjekapital registrert 2026-03-17.

KYSTANLEGG AS is registered as a limited company in Rana, Nordland with organisation number 930637971. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Kystrelaterte entreprenørtjenester, herunder utleie av anleggsmidler, samt virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 873,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 873,000
Equity
NOK 1.1m
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.1%
Good
Equity as a share of total capital

Who owns KYSTANLEGG AS?

MHR HOLDING AS
KYSTANLEGG AS
NOK 1.4m rev. · NOK 873,000 profit

KYSTANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KYSTANLEGG AS

Who owns KYSTANLEGG AS?

MHR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KYSTANLEGG AS?

KYSTANLEGG AS had revenue of NOK 1.4m in 2024.

Who is the general manager of KYSTANLEGG AS?

Marius Heien Reinsnes is registered as general manager of KYSTANLEGG AS.

Where is KYSTANLEGG AS based?

KYSTANLEGG AS has its business address in Mo I Rana.

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.