BIZTRAC BETA
Rental and operating of own or leased real estate

KGH FEVANG EIENDOM AS

Org. no. 999650090 Limited company (AS) Sandefjord Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 544,000
Operating profit NOK 365,000
Equity NOK 1.8m
Incorporated 2013
Share capital NOK 100,000

KGH FEVANG EIENDOM AS is registered as a limited company in Sandefjord, Vestfold with organisation number 999650090. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling, salg samt utleie av eiendommer med tilhørende tjenester. Selskapet skal også kunne inneha eierinteresser i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 544,000 in revenue and NOK 365,000 in operating profit.

Key figures · 2024

Revenue
NOK 544,000
Operating profit
NOK 365,000
Equity
NOK 1.8m
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.6%
Good
Equity as a share of total capital

Who owns KGH FEVANG EIENDOM AS?

KJELL GUNNAR FEVANG
KGH FEVANG EIENDOM AS
NOK 544,000 rev. · NOK 365,000 profit

KGH FEVANG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KGH FEVANG EIENDOM AS own?

KGH FEVANG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KGH FEVANG EIENDOM AS

Who owns KGH FEVANG EIENDOM AS?

KJELL GUNNAR FEVANG is the largest registered owner, with 60.0%.

What is the revenue of KGH FEVANG EIENDOM AS?

KGH FEVANG EIENDOM AS had revenue of NOK 544,000 in 2024.

Where is KGH FEVANG EIENDOM AS based?

KGH FEVANG EIENDOM AS has its business address in Andebu.

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.