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

SKRUF INVEST AS

Org. no. 919071648 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 1.2m
Incorporated 2017
Share capital NOK 30,000

Signals

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

SKRUF INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 919071648. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap.”.

Key figures · 2025

Operating profit
NOK −11,000
▼ −833 %
Equity
NOK 1.2m
▲ +6 %
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns SKRUF INVEST AS?

SKRUF INVEST AS
· NOK −11,000 profit

SKRUF INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKRUF INVEST AS own?

SKRUF INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SKRUF INVEST AS

Who owns SKRUF INVEST AS?

KENNETH ÅRSETH NEPSTAD is the largest registered owner, with 100.0%.

Where is SKRUF INVEST AS based?

SKRUF INVEST AS has its business address in Rådal.

Property

Business address Hjortevegen 16A, 5236 Rådal
Cadastral unit 4601-40/624/0/0
Building Rekkehus · 1 unit

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.