biztrac. BETA
COMPANY REGISTER PROFILE
917134995 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SKORHAUGÅSEN AS

Org. no. 917134995 Limited company (AS) Nordre Follo Incorporated 2016 Active
Revenue 2025 NOK 369,000
Operating profit NOK −5,000
Equity NOK 5.4m
Incorporated 2016
Share capital NOK 3.0m

Signals

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

SKORHAUGÅSEN AS is registered as a limited company in Nordre Follo, Akershus with organisation number 917134995. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 3.0m, divided into 10000 shares. The company's stated purpose is: “Investering i og deltakelse i andre virksomheter, samt investering i fast eiendom og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 369,000 in revenue and NOK −5,000 in operating profit.

Former names: BAKKEVEIEN AS

Key figures · 2025

Revenue
NOK 369,000
▲ +22 %
Operating profit
NOK −5,000
▼ −108 %
Equity
NOK 5.4m
▼ −6 %
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
0.4%
Not satisfactory
Return on total assets
Solidity
46.2%
Very good
Equity as a share of total capital

Who owns SKORHAUGÅSEN AS?

SKORHAUGÅSEN AS
NOK 369,000 rev. · NOK −5,000 profit

SKORHAUGÅSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKORHAUGÅSEN AS

Who owns SKORHAUGÅSEN AS?

VINKL AS is the largest registered owner, with 100.0%.

What is the revenue of SKORHAUGÅSEN AS?

SKORHAUGÅSEN AS had revenue of NOK 369,000 in 2025.

Where is SKORHAUGÅSEN AS based?

SKORHAUGÅSEN AS has its business address in Ski.

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.