BIZTRAC BETA
COMPANY REGISTER PROFILE
920202780 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

STOKKAASEN AS

Org. no. 920202780 Limited company (AS) Nordre Follo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 19.4m
Incorporated 2017
Share capital NOK 30,000

Signals

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

STOKKAASEN AS is registered as a limited company in Nordre Follo, Akershus with organisation number 920202780. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringsvirksomhet. Kjøp, salg og utleie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK 19.4m
Est. value
NOK 17.7m

Financial health · 2025

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

Who owns STOKKAASEN AS?

STOKKAASEN AS
· NOK −16,000 profit

STOKKAASEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOKKAASEN AS

Who owns STOKKAASEN AS?

JON OLA STOKKE is the largest registered owner, with 100.0%.

Where is STOKKAASEN AS based?

STOKKAASEN AS has its business address in Kolbotn.

Property

Business address Johan Halvorsens vei 16, 1410 Kolbotn
Cadastral unit 3207-247/97/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.