biztrac. BETA
COMPANY REGISTER PROFILE
925544493 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

SKRYME AS

Org. no. 925544493 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 12.9m
Incorporated 2020
Share capital NOK 303,000

Signals

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

SKRYME AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925544493. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 303,000, divided into 1000 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskaper, samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
▲ +17 %
Equity
NOK 12.9m
▲ +28 %
Est. value
NOK 58.2m

Financial health · 2025

Liquidity
3.09
Very good
Current assets ÷ current liabilities
Profitability
52.2%
Very good
Return on total assets
Solidity
87.4%
Very good
Equity as a share of total capital

Who owns SKRYME AS?

SKRYME AS
NOK 0 rev. · NOK −28,000 profit

SKRYME AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SKRYME AS own?

SKRYME AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKRYME AS

Who owns SKRYME AS?

Vilmer Kopreitan is the largest registered owner, with 99.9%.

What is the revenue of SKRYME AS?

SKRYME AS had revenue of NOK 0 in 2025.

Who is the general manager of SKRYME AS?

Vilmer Kopreitan is registered as general manager of SKRYME AS.

Where is SKRYME AS based?

SKRYME AS has its business address in Trondheim.

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.