biztrac. BETA
COMPANY REGISTER PROFILE
998191564 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Activities of religious organisations

STORSTUA OMSORGS- OG KONFERANSESENTER

Org. no. 998191564 Association/club/organisation (FLI) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 12.5m
Operating profit NOK 420,000
Equity NOK 661,000
Incorporated 2012
Employees 8

STORSTUA OMSORGS- OG KONFERANSESENTER is registered as a association/club/organisation in Asker, Akershus with organisation number 998191564. The business is classified under activities of religious organisations (NACE 94.910). The company was incorporated in 2012 and has 8 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 12.5m in revenue and NOK 420,000 in operating profit.

Former names: HALLINGSKARVET OMSORG OG KONFERANSESENTER

Key figures · 2025

Revenue
NOK 12.5m
▲ +14 %
Operating profit
NOK 420,000
▲ +171 %
Equity
NOK 661,000
▲ +170 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
17.2%
Very good
Return on total assets
Solidity
27.4%
Good
Equity as a share of total capital

Who owns STORSTUA OMSORGS- OG KONFERANSESENTER?

No shareholders are registered for STORSTUA OMSORGS- OG KONFERANSESENTER in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STORSTUA OMSORGS- OG KONFERANSESENTER

What is the revenue of STORSTUA OMSORGS- OG KONFERANSESENTER?

STORSTUA OMSORGS- OG KONFERANSESENTER had revenue of NOK 12.5m in 2025.

Who is the general manager of STORSTUA OMSORGS- OG KONFERANSESENTER?

Heidi Korneliussen is registered as general manager of STORSTUA OMSORGS- OG KONFERANSESENTER.

Where is STORSTUA OMSORGS- OG KONFERANSESENTER based?

STORSTUA OMSORGS- OG KONFERANSESENTER has its business address in Røyken.

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.