BIZTRAC BETA
Buying and selling of own real estate

KLYVEGÅRDEN AS

Org. no. 997442563 Limited company (AS) Holmestrand Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 23,000
Operating profit NOK 14,000
Equity NOK 118,000
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KLYVEGÅRDEN AS is registered as a limited company in Holmestrand, Vestfold with organisation number 997442563. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, drift og salg av eiendommer med tilhørende virksomheter, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 23,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 23,000
Operating profit
NOK 14,000
Equity
NOK 118,000
Est. value
NOK 118,000

Financial health · 2025

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

Who owns KLYVEGÅRDEN AS?

EESS AS
KLYVEGÅRDEN AS
NOK 23,000 rev. · NOK 14,000 profit

KLYVEGÅRDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLYVEGÅRDEN AS

Who owns KLYVEGÅRDEN AS?

EESS AS is the largest registered owner, with 100.0%.

What is the revenue of KLYVEGÅRDEN AS?

KLYVEGÅRDEN AS had revenue of NOK 23,000 in 2025.

Who is the general manager of KLYVEGÅRDEN AS?

Jens-Petter Sørebø Aven is registered as general manager of KLYVEGÅRDEN AS.

Where is KLYVEGÅRDEN AS based?

KLYVEGÅRDEN AS has its business address in Holmestrand.

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.