BIZTRAC BETA
Development of building projects

HESBY EIENDOM OG HOLDING AS

Org. no. 967870145 Limited company (AS) Tønsberg Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 892,000
Operating profit NOK 19,000
Equity NOK 7.1m
Incorporated 1993
Share capital NOK 250,000

HESBY EIENDOM OG HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 967870145. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1993. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Deltakelse i andre virksomheter og kjøp og salg av verdipapirer, og alt som hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 892,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 892,000
Operating profit
NOK 19,000
Equity
NOK 7.1m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns HESBY EIENDOM OG HOLDING AS?

MORTEN EVENSEN
HESBY EIENDOM OG HOLDING AS
NOK 892,000 rev. · NOK 19,000 profit

HESBY EIENDOM OG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HESBY EIENDOM OG HOLDING AS own?

HESBY EIENDOM OG HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HESBY EIENDOM OG HOLDING AS

Who owns HESBY EIENDOM OG HOLDING AS?

MORTEN EVENSEN is the largest registered owner, with 100.0%.

What is the revenue of HESBY EIENDOM OG HOLDING AS?

HESBY EIENDOM OG HOLDING AS had revenue of NOK 892,000 in 2025.

Where is HESBY EIENDOM OG HOLDING AS based?

HESBY EIENDOM OG HOLDING AS has its business address in Tønsberg.

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.