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

MELDERSKIN INVEST AS

Org. no. 935762383 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −9
Equity NOK 5.8m
Incorporated 2025
Share capital NOK 5.0m

Signals

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

MELDERSKIN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 935762383. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 5.0m, divided into 5000 shares. The company's stated purpose is: “Investeringsselskap, som driver investeringsvirksomhet i verdipapirer og virksomhet forbundet med dette.”.

Key figures · 2025

Operating profit
NOK −9
Equity
NOK 5.8m
Est. value
NOK 7.3m

Financial health · 2025

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

Who owns MELDERSKIN INVEST AS?

MELDERSKIN INVEST AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about MELDERSKIN INVEST AS

Who owns MELDERSKIN INVEST AS?

KAD-INVEST AS is the largest registered owner, with 51.0%.

Where is MELDERSKIN INVEST AS based?

MELDERSKIN INVEST AS has its business address in Oslo.

Property

Business address Olav Aukrusts vei 4C, 0785 Oslo
Cadastral unit 301-27/2239/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 16 units

3 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.