BIZTRAC BETA
Development of building projects

PILOTVEIEN 4 AS

Org. no. 917336202 Limited company (AS) Kristiansund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 2.4m
Equity NOK 5.6m
Incorporated 2016
Share capital NOK 134,000

Signals

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

PILOTVEIEN 4 AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 917336202. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 134,000, divided into 100000 shares. The company's stated purpose is: “Ervervelse og utvikling av tomter og eiendommer for utleie og salg, samt drive slik aktivitet som naturlig faller innunder dette, herunder å eie andeler i andre selskap med tilsvarende aktivitet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 2.4m
Equity
NOK 5.6m
Est. value
NOK 8.8m

Financial health · 2024

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

Who owns PILOTVEIEN 4 AS?

KRISTIANSUND NÆRINGSPARK AS
PILOTVEIEN 4 AS
NOK 2.6m rev. · NOK 2.4m profit

PILOTVEIEN 4 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PILOTVEIEN 4 AS

Who owns PILOTVEIEN 4 AS?

KRISTIANSUND NÆRINGSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of PILOTVEIEN 4 AS?

PILOTVEIEN 4 AS had revenue of NOK 2.6m in 2024.

Where is PILOTVEIEN 4 AS based?

PILOTVEIEN 4 AS has its business address in Kristiansund N.

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.