BIZTRAC BETA
COMPANY REGISTER PROFILE
930080861 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Computer consultancy and computer facilities management activities

SKRIVEN AS

Org. no. 930080861 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

SKRIVEN AS is registered as a limited company in Oslo, Oslo with organisation number 930080861. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Teknologi-rådgivning.”.

Key figures · 2024

Equity
NOK 30,000
Est. value
NOK 54,000

Financial health · 2024

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

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

Who owns SKRIVEN AS?

SKRIVEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKRIVEN AS

Who owns SKRIVEN AS?

SVEN OLE SKRIVERVIK is the largest registered owner, with 100.0%.

Who is the general manager of SKRIVEN AS?

Sven Ole Skrivervik is registered as general manager of SKRIVEN AS.

Where is SKRIVEN AS based?

SKRIVEN AS has its business address in Oslo.

Property

Business address Åsstubben 68, 0381 Oslo
Cadastral unit 301-28/1080/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 13 units

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