BIZTRAC BETA
Other technical consultancy

NORDÅSDALEN 22 AS

Org. no. 952573535 Limited company (AS) Bergen Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK −1.5m
Equity NOK 2.6m
Incorporated 1989
Share capital NOK 2.9m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORDÅSDALEN 22 AS is registered as a limited company in Bergen, Vestland with organisation number 952573535. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1989. Registered share capital is NOK 2.9m, divided into 28640 shares. The company's stated purpose is: “Eiendomsutvikling og det som derav følger. ”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK −1.5m
Equity
NOK 2.6m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns NORDÅSDALEN 22 AS?

BERGEN BYGG AS
NORDÅSDALEN 22 AS
NOK 6.3m rev. · NOK −1.5m profit

NORDÅSDALEN 22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDÅSDALEN 22 AS

Who owns NORDÅSDALEN 22 AS?

BERGEN BYGG AS is the largest registered owner, with 100.0%.

What is the revenue of NORDÅSDALEN 22 AS?

NORDÅSDALEN 22 AS had revenue of NOK 6.3m in 2024.

Who is the general manager of NORDÅSDALEN 22 AS?

Jan Willy Rasmussen is registered as general manager of NORDÅSDALEN 22 AS.

Where is NORDÅSDALEN 22 AS based?

NORDÅSDALEN 22 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.