BIZTRAC BETA
Construction of residential and non-residential buildings

FELEHOVET UTVIKLING AS

Org. no. 923605452 Limited company (AS) Nissedal Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK −44,000
Equity NOK 997,000
Incorporated 2019
Share capital NOK 1.0m

Signals

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

FELEHOVET UTVIKLING AS is registered as a limited company in Nissedal, Telemark with organisation number 923605452. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Eigedomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −44,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK −44,000
Equity
NOK 997,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns FELEHOVET UTVIKLING AS?

AKADEMIKERBONDEN AS
FELEHOVET UTVIKLING AS
NOK 5,000 rev. · NOK −44,000 profit

FELEHOVET UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FELEHOVET UTVIKLING AS

Who owns FELEHOVET UTVIKLING AS?

AKADEMIKERBONDEN AS is the largest registered owner, with 60.0%.

What is the revenue of FELEHOVET UTVIKLING AS?

FELEHOVET UTVIKLING AS had revenue of NOK 5,000 in 2025.

Who is the general manager of FELEHOVET UTVIKLING AS?

Sverre Tveit is registered as general manager of FELEHOVET UTVIKLING AS.

Where is FELEHOVET UTVIKLING AS based?

FELEHOVET UTVIKLING AS has its business address in Treungen.

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.