BIZTRAC BETA
Civil engineering activities

SØNNAVIND CONSULT AS

Org. no. 923488189 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 794,000
Operating profit NOK −8,000
Equity NOK 139,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

SØNNAVIND CONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 923488189. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulent og rådgivningsvirksomhet innenfor bygg og eiendom, samt tilhørende virksomheter. Prosjektledelse og eiendomsutvikling. Ansvarlig søker Byggelånskotroll. Uavhengig kontroll skisse/tegninger. Investeringer i eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 794,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 794,000
Operating profit
NOK −8,000
Equity
NOK 139,000
Est. value
NOK 901,000

Financial health · 2024

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

Who owns SØNNAVIND CONSULT AS?

JANNECKE CHRISTINE ROSTOCK RØDSETH
SØNNAVIND CONSULT AS
NOK 794,000 rev. · NOK −8,000 profit

SØNNAVIND CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØNNAVIND CONSULT AS

Who owns SØNNAVIND CONSULT AS?

JANNECKE CHRISTINE ROSTOCK RØDSETH is the largest registered owner, with 100.0%.

What is the revenue of SØNNAVIND CONSULT AS?

SØNNAVIND CONSULT AS had revenue of NOK 794,000 in 2025.

Where is SØNNAVIND CONSULT AS based?

SØNNAVIND CONSULT AS has its business address in Oslo.

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.