BIZTRAC BETA
Silviculture and other forestry activities

OFTENES VED AS

Org. no. 932212064 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 264,000
Operating profit NOK −88,000
Equity NOK −10,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−10k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−88k kr).

OFTENES VED AS is registered as a limited company in Kristiansand, Agder with organisation number 932212064. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 6000 shares. The company's stated purpose is: “Salg av ved.”. The most recent filed accounts, for the 2025 financial year, show NOK 264,000 in revenue and NOK −88,000 in operating profit.

Key figures · 2025

Revenue
NOK 264,000
Operating profit
NOK −88,000
Equity
NOK −10,000

Financial health · 2025

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

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

Who owns OFTENES VED AS?

JONAS NYGÅRD
OFTENES VED AS
NOK 264,000 rev. · NOK −88,000 profit

OFTENES VED AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about OFTENES VED AS

Who owns OFTENES VED AS?

JONAS NYGÅRD is the largest registered owner, with 20.0%.

What is the revenue of OFTENES VED AS?

OFTENES VED AS had revenue of NOK 264,000 in 2025.

Who is the general manager of OFTENES VED AS?

Stian Nygård is registered as general manager of OFTENES VED AS.

Where is OFTENES VED AS based?

OFTENES VED AS has its business address in Søgne.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.