BIZTRAC BETA
Buying and selling of own real estate

JANAFLATEN NÆRINGSPARK AS

Org. no. 922608202 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 14.1m
Operating profit NOK 8.6m
Equity NOK 134.9m
Incorporated 2019
Share capital NOK 1.5m

Signals

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

JANAFLATEN NÆRINGSPARK AS is registered as a limited company in Bergen, Vestland with organisation number 922608202. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 1.5m, divided into 100 shares. The company's stated purpose is: “Næringsdrift, i hovedsak kjøp og salg av fast eiendom og alt hva herved er forbundet, investeringsvirksomhet og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.1m in revenue and NOK 8.6m in operating profit.

Key figures · 2024

Revenue
NOK 14.1m
Operating profit
NOK 8.6m
Equity
NOK 134.9m
Est. value
NOK 107.0m

Financial health · 2024

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

Who owns JANAFLATEN NÆRINGSPARK AS?

MIDGARD VEST AS
JANAFLATEN NÆRINGSPARK AS
NOK 14.1m rev. · NOK 8.6m profit

JANAFLATEN NÆRINGSPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JANAFLATEN NÆRINGSPARK AS

Who owns JANAFLATEN NÆRINGSPARK AS?

MIDGARD VEST AS is the largest registered owner, with 100.0%.

What is the revenue of JANAFLATEN NÆRINGSPARK AS?

JANAFLATEN NÆRINGSPARK AS had revenue of NOK 14.1m in 2024.

Where is JANAFLATEN NÆRINGSPARK AS based?

JANAFLATEN NÆRINGSPARK AS has its business address in Bergen.

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.