BIZTRAC BETA
Rental and operating of own or leased real estate

SMITEK EIENDOM AS

Org. no. 921176147 Limited company (AS) Østre Toten Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 974,000
Equity NOK 1.8m
Incorporated 2018
Share capital NOK 600,000

SMITEK EIENDOM AS is registered as a limited company in Østre Toten, Innlandet with organisation number 921176147. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Eie og drift av fast eiendom, investering i verdipapirer samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 974,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 974,000
Equity
NOK 1.8m
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.5%
Satisfactory
Equity as a share of total capital

Who owns SMITEK EIENDOM AS?

MORTEN SMEDSHAMMER
SMITEK EIENDOM AS
NOK 1.5m rev. · NOK 974,000 profit

SMITEK EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Group structure

SMITEK EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about SMITEK EIENDOM AS

Who owns SMITEK EIENDOM AS?

MORTEN SMEDSHAMMER is the largest registered owner, with 50.0%.

What is the revenue of SMITEK EIENDOM AS?

SMITEK EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of SMITEK EIENDOM AS?

Kjetil Evenstuen is registered as general manager of SMITEK EIENDOM AS.

Where is SMITEK EIENDOM AS based?

SMITEK EIENDOM AS has its business address in Lena.

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.