BIZTRAC BETA
Business and other management consultancy activities

SIRVENTE AS

Org. no. 876330482 Limited company (AS) Hvaler Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 4,000
Operating profit NOK −40,000
Equity NOK 180,000
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−40k kr).

SIRVENTE AS is registered as a limited company in Hvaler, Østfold with organisation number 876330482. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Yte konsulenttjenester innenfor områdene informasjon og organisasjonsutvikling i offentlig, privat og frivillig sektor, samt deltakelse i annen virksomhet som hermed er forenlig.”. The most recent filed accounts, for the 2024 financial year, show NOK 4,000 in revenue and NOK −40,000 in operating profit.

Key figures · 2024

Revenue
NOK 4,000
Operating profit
NOK −40,000
Equity
NOK 180,000
Est. value
NOK 488,000

Financial health · 2024

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

Who owns SIRVENTE AS?

NINA SOLBERG
SIRVENTE AS
NOK 4,000 rev. · NOK −40,000 profit

SIRVENTE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIRVENTE AS own?

SIRVENTE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIRVENTE AS

Who owns SIRVENTE AS?

NINA SOLBERG is the largest registered owner, with 100.0%.

What is the revenue of SIRVENTE AS?

SIRVENTE AS had revenue of NOK 4,000 in 2024.

Where is SIRVENTE AS based?

SIRVENTE AS has its business address in Skjærhalden.

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.