biztrac. BETA
COMPANY REGISTER PROFILE
922608202 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

JANAFLATEN NÆRINGSPARK AS

Org. no. 922608202 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 16.9m
Operating profit NOK 11.0m
Equity NOK 137.3m
Incorporated 2019
Share capital NOK 1.5m

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 2025 financial year, show NOK 16.9m in revenue and NOK 11.0m in operating profit.

Former names: JANAFLATEN 9 AS

Key figures · 2025

Revenue
NOK 16.9m
▲ +20 %
Operating profit
NOK 11.0m
▲ +29 %
Equity
NOK 137.3m
▲ +2 %
Est. value
NOK 106.4m

Financial health · 2025

Liquidity
0.41
Not satisfactory
Current assets ÷ current liabilities
Profitability
3.7%
Weak
Return on total assets
Solidity
48.0%
Very good
Equity as a share of total capital

Who owns JANAFLATEN NÆRINGSPARK AS?

JANAFLATEN NÆRINGSPARK AS
NOK 16.9m rev. · NOK 11.0m 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 16.9m in 2025.

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 03.10.2026.

Report a problem

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