BIZTRAC BETA
Development of building projects

SMET EIENDOM AS

Org. no. 927018187 Limited company (AS) Holmestrand Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 564,000
Operating profit NOK 77,000
Equity NOK 298,000
Incorporated 2021
Share capital NOK 30,000

SMET EIENDOM AS is registered as a limited company in Holmestrand, Vestfold with organisation number 927018187. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og drift av eiendom, samt annen virksomhet som naturlig hører sammen med dette, herunder å delta i andre selskap, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 564,000 in revenue and NOK 77,000 in operating profit.

Key figures · 2025

Revenue
NOK 564,000
Operating profit
NOK 77,000
Equity
NOK 298,000
Est. value
NOK 413,000

Financial health · 2025

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

Who owns SMET EIENDOM AS?

ARTUR SMET
SMET EIENDOM AS
NOK 564,000 rev. · NOK 77,000 profit

SMET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMET EIENDOM AS

Who owns SMET EIENDOM AS?

ARTUR SMET is the largest registered owner, with 100.0%.

What is the revenue of SMET EIENDOM AS?

SMET EIENDOM AS had revenue of NOK 564,000 in 2025.

Who is the general manager of SMET EIENDOM AS?

Artur Smet is registered as general manager of SMET EIENDOM AS.

Where is SMET EIENDOM AS based?

SMET EIENDOM 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.