BIZTRAC BETA
Development of building projects

BORGEGRENDA UTVIKLING AS

Org. no. 922859574 Limited company (AS) Skien Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −617,000
Equity NOK 626,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

BORGEGRENDA UTVIKLING AS is registered as a limited company in Skien, Telemark with organisation number 922859574. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling av boliger samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −617,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −617,000
Equity
NOK 626,000
Est. value
NOK 571,000

Financial health · 2025

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

Who owns BORGEGRENDA UTVIKLING AS?

FIHA HOLDING AS
BORGEGRENDA UTVIKLING AS
NOK 0 rev. · NOK −617,000 profit

BORGEGRENDA UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGEGRENDA UTVIKLING AS

Who owns BORGEGRENDA UTVIKLING AS?

FIHA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BORGEGRENDA UTVIKLING AS?

BORGEGRENDA UTVIKLING AS had revenue of NOK 0 in 2025.

Who is the general manager of BORGEGRENDA UTVIKLING AS?

Arve Haugseter is registered as general manager of BORGEGRENDA UTVIKLING AS.

Where is BORGEGRENDA UTVIKLING AS based?

BORGEGRENDA UTVIKLING AS has its business address in Skien.

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.