BIZTRAC BETA
Development of building projects

SNØBYEN UTVIKLING AS

Org. no. 998186730 Limited company (AS) Lørenskog Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 35.4m
Operating profit NOK 14.2m
Equity NOK 136.8m
Incorporated 2012
Share capital NOK 1.6m

SNØBYEN UTVIKLING AS is registered as a limited company in Lørenskog, Akershus with organisation number 998186730. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 1.6m, divided into 2077126 shares. The company's stated purpose is: “Selv, eller gjennom datterselskaper, å utvikle en helårlig vinterdestinasjon i Lørenskog Kommune med tilhørende næring og boliger.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.4m in revenue and NOK 14.2m in operating profit.

Key figures · 2024

Revenue
NOK 35.4m
Operating profit
NOK 14.2m
Equity
NOK 136.8m
Est. value
NOK 115.8m

Financial health · 2024

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

Who owns SNØBYEN UTVIKLING AS?

SNØBYEN AS
SNØBYEN UTVIKLING AS
NOK 35.4m rev. · NOK 14.2m profit

SNØBYEN UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SNØBYEN UTVIKLING AS er morselskap for 8 datterselskaper:

Frequently asked questions about SNØBYEN UTVIKLING AS

Who owns SNØBYEN UTVIKLING AS?

SNØBYEN AS is the largest registered owner, with 100.0%.

What is the revenue of SNØBYEN UTVIKLING AS?

SNØBYEN UTVIKLING AS had revenue of NOK 35.4m in 2024.

Who is the general manager of SNØBYEN UTVIKLING AS?

Katharina Ræder Endresen Hernæs is registered as general manager of SNØBYEN UTVIKLING AS.

Where is SNØBYEN UTVIKLING AS based?

SNØBYEN UTVIKLING AS has its business address in Lørenskog.

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.