BIZTRAC BETA
Rental and operating of own or leased real estate

EKHOLDT EIENDOM AS

Org. no. 896792962 Limited company (AS) Krødsherad Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 702,000
Equity NOK 860,000
Incorporated 2011
Share capital NOK 100,000

EKHOLDT EIENDOM AS is registered as a limited company in Krødsherad, Buskerud with organisation number 896792962. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er kjøp og salg av fast eiendom, samt oppføring av bygg og utleie av fast eiendom. Eie aksjer/andeler i andre selskaper, samt alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 702,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 702,000
Equity
NOK 860,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns EKHOLDT EIENDOM AS?

VEGARD EKHOLDT
EKHOLDT EIENDOM AS
NOK 1.4m rev. · NOK 702,000 profit

EKHOLDT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EKHOLDT EIENDOM AS

Who owns EKHOLDT EIENDOM AS?

VEGARD EKHOLDT is the largest registered owner, with 100.0%.

What is the revenue of EKHOLDT EIENDOM AS?

EKHOLDT EIENDOM AS had revenue of NOK 1.4m in 2025.

Who is the general manager of EKHOLDT EIENDOM AS?

Vegard Ekholdt is registered as general manager of EKHOLDT EIENDOM AS.

Where is EKHOLDT EIENDOM AS based?

EKHOLDT EIENDOM AS has its business address in Krøderen.

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.