BIZTRAC BETA
COMPANY REGISTER PROFILE
936133401 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SKARVIN INVEST AS

Org. no. 936133401 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 22.5m
Incorporated 2025
Share capital NOK 30,000

Signals

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

SKARVIN INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 936133401. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Erverve og eie aksjer og andeler i andre selskaper, handel i finansielle instrumenter samt all annen virksomhet som naturlig hører derved.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 22.5m
Est. value
NOK 13.2m

Financial health · 2025

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

Who owns SKARVIN INVEST AS?

SKARVIN INVEST AS
NOK 0 rev. · NOK −6,000 profit

SKARVIN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKARVIN INVEST AS own?

SKARVIN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKARVIN INVEST AS

Who owns SKARVIN INVEST AS?

PER ERIK MEDHUS is the largest registered owner, with 100.0%.

What is the revenue of SKARVIN INVEST AS?

SKARVIN INVEST AS had revenue of NOK 0 in 2025.

Where is SKARVIN INVEST AS based?

SKARVIN INVEST AS has its business address in Lommedalen.

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

Report a problem

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