BIZTRAC BETA
Rental and operating of own or leased real estate

SMH KLOKKERJORDET AS

Org. no. 922423350 Limited company (AS) Holmestrand Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK 4.3m
Equity NOK 538,000
Incorporated 2019
Share capital NOK 100,000

SMH KLOKKERJORDET AS is registered as a limited company in Holmestrand, Vestfold with organisation number 922423350. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Kjøp, utvikling, bygging, utleie og salg av fast eiendom, samt deltakelse i andre selskaper innenfor dagens grense for Sande kommune i Vestfold.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 4.3m in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
Operating profit
NOK 4.3m
Equity
NOK 538,000
Est. value
NOK 7.7m

Financial health · 2025

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

Who owns SMH KLOKKERJORDET AS?

AS SANDE MEIERI HANDELSLAG
SMH KLOKKERJORDET AS
NOK 5.7m rev. · NOK 4.3m profit

SMH KLOKKERJORDET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMH KLOKKERJORDET AS

Who owns SMH KLOKKERJORDET AS?

AS SANDE MEIERI HANDELSLAG is the largest registered owner, with 100.0%.

What is the revenue of SMH KLOKKERJORDET AS?

SMH KLOKKERJORDET AS had revenue of NOK 5.7m in 2025.

Who is the general manager of SMH KLOKKERJORDET AS?

Ole Kind is registered as general manager of SMH KLOKKERJORDET AS.

Where is SMH KLOKKERJORDET AS based?

SMH KLOKKERJORDET AS has its business address in Sande I Vestfold.

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.