BIZTRAC BETA
COMPANY REGISTER PROFILE
926443984 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SKIMRE AS

Org. no. 926443984 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 21,000
Incorporated 2021
Share capital NOK 30,000

SKIMRE AS is registered as a limited company in Bærum, Akershus with organisation number 926443984. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andre verdipapirer, samt kjøp, salg og utleie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 21,000
Est. value
NOK 25,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SKIMRE AS?

SKIMRE AS
· NOK 0 profit

SKIMRE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKIMRE AS own?

SKIMRE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKIMRE AS

Who owns SKIMRE AS?

STIAN HAMRE SKISTAD is the largest registered owner, with 100.0%.

Where is SKIMRE AS based?

SKIMRE AS has its business address in Slependen.

Property

Business address Gyssestadkollen 1, 1341 Slependen
Cadastral unit 3201-53/162/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

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.