biztrac. BETA
COMPANY REGISTER PROFILE
929296303 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

SKRAIB AS

Org. no. 929296303 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 202,000
Operating profit NOK 15,000
Equity NOK 119,000
Incorporated 2022
Share capital NOK 30,000

SKRAIB AS is registered as a limited company in Oslo, Oslo with organisation number 929296303. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning, konsulenttjenester, virksomhetstjenester og andre produkter og tjenester til bedrifter og privatpersoner, samt delta i andre virksomheter og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 202,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 202,000
▼ −47 %
Operating profit
NOK 15,000
▼ −90 %
Equity
NOK 119,000
▲ +15 %
Est. value
NOK 205,000

Financial health · 2025

Liquidity
2.01
Very good
Current assets ÷ current liabilities
Profitability
5.7%
Weak
Return on total assets
Solidity
39.4%
Good
Equity as a share of total capital

Who owns SKRAIB AS?

SKRAIB AS
NOK 202,000 rev. · NOK 15,000 profit

SKRAIB AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKRAIB AS own?

SKRAIB AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about SKRAIB AS

Who owns SKRAIB AS?

VEVIOS AS is the largest registered owner, with 100.0%.

What is the revenue of SKRAIB AS?

SKRAIB AS had revenue of NOK 202,000 in 2025.

Where is SKRAIB AS based?

SKRAIB AS has its business address in Oslo.

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.