BIZTRAC BETA
Rental and operating of own or leased real estate

SMEDSTUEN KT EIENDOM AS

Org. no. 929999002 Limited company (AS) Ringsaker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 628,000
Operating profit NOK 408,000
Equity NOK 937,000
Incorporated 2022
Share capital NOK 930,000

SMEDSTUEN KT EIENDOM AS is registered as a limited company in Ringsaker, Innlandet with organisation number 929999002. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 930,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom og hva som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 628,000 in revenue and NOK 408,000 in operating profit.

Key figures · 2025

Revenue
NOK 628,000
Operating profit
NOK 408,000
Equity
NOK 937,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns SMEDSTUEN KT EIENDOM AS?

SMEDSTUEN HOLDING AS
SMEDSTUEN KT EIENDOM AS
NOK 628,000 rev. · NOK 408,000 profit

SMEDSTUEN KT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMEDSTUEN KT EIENDOM AS

Who owns SMEDSTUEN KT EIENDOM AS?

SMEDSTUEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SMEDSTUEN KT EIENDOM AS?

SMEDSTUEN KT EIENDOM AS had revenue of NOK 628,000 in 2025.

Who is the general manager of SMEDSTUEN KT EIENDOM AS?

Ole Christian Smedstuen is registered as general manager of SMEDSTUEN KT EIENDOM AS.

Where is SMEDSTUEN KT EIENDOM AS based?

SMEDSTUEN KT EIENDOM AS has its business address in Moelv.

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.