BIZTRAC BETA
Buying and selling of own real estate

ANNEKSET EIENDOM AS

Org. no. 988593877 Limited company (AS) Hol Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 288,000
Operating profit NOK 103,000
Equity NOK 391,000
Incorporated 2005
Share capital NOK 100,000

ANNEKSET EIENDOM AS is registered as a limited company in Hol, Buskerud with organisation number 988593877. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, herunder utleie av fast eiendom, samt hva hermed står i forbindelse, investeringer i annen virksomhet herunder deltakelse i andre selskaper med lignende virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 288,000 in revenue and NOK 103,000 in operating profit.

Key figures · 2024

Revenue
NOK 288,000
Operating profit
NOK 103,000
Equity
NOK 391,000
Est. value
NOK 443,000

Financial health · 2024

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.9%
Good
Equity as a share of total capital

Who owns ANNEKSET EIENDOM AS?

GERD KOLTERUD
ANNEKSET EIENDOM AS
NOK 288,000 rev. · NOK 103,000 profit

ANNEKSET EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ANNEKSET EIENDOM AS

Who owns ANNEKSET EIENDOM AS?

GERD KOLTERUD is the largest registered owner, with 50.0%.

What is the revenue of ANNEKSET EIENDOM AS?

ANNEKSET EIENDOM AS had revenue of NOK 288,000 in 2024.

Who is the general manager of ANNEKSET EIENDOM AS?

Gerd Kolterud is registered as general manager of ANNEKSET EIENDOM AS.

Where is ANNEKSET EIENDOM AS based?

ANNEKSET EIENDOM AS has its business address in Geilo.

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.