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

AS VERVEN

Org. no. 960533399 Limited company (AS) Bygland Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 2.6m
Incorporated 1991
Share capital NOK 450,000

Signals

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

AS VERVEN is registered as a limited company in Bygland, Agder with organisation number 960533399. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1991. Registered share capital is NOK 450,000, divided into 4500 shares. The company's stated purpose is: “Virksomhet innen bedriftsrådgivning og konsulent- tjenester og alt som derved står i forbindelse, samt deltakelse i andre selskaper enten ved aksje- eie eller kjøp.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −5,000
▲ +74 %
Equity
NOK 2.6m
▲ +8 %
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
184.97
Very good
Current assets ÷ current liabilities
Profitability
15.6%
Very good
Return on total assets
Solidity
99.5%
Very good
Equity as a share of total capital

Who owns AS VERVEN?

AS VERVEN has 3 registered shareholders:

All shareholders and roles →

Which companies does AS VERVEN own?

AS VERVEN holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AS VERVEN

Who owns AS VERVEN?

Olav Sagemo is the largest registered owner, with 66.0%.

What is the revenue of AS VERVEN?

AS VERVEN had revenue of NOK 0 in 2025.

Where is AS VERVEN based?

AS VERVEN has its business address in Bygland.

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.