BIZTRAC BETA
Uoppgitt

SMIDESANG EIENDOM AS

Org. no. 911905000 Limited company (AS) Lillehammer Incorporated 1965 Active
Ownership graph ↗
Revenue 2025 NOK 829,000
Operating profit NOK 597,000
Equity NOK 4.7m
Incorporated 1965
Share capital NOK 380,000

SMIDESANG EIENDOM AS is registered as a limited company in Lillehammer, Innlandet with organisation number 911905000. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1965. Registered share capital is NOK 380,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av kjøretøy og valuta, kjøp og salg av eiendom samt drift av eiendom og hva dermed står i forbindelse, samt ved aksjetegning eller på annen måte gjøre seg interessert i annen virksomhet i inn og utland.”. The most recent filed accounts, for the 2025 financial year, show NOK 829,000 in revenue and NOK 597,000 in operating profit.

Key figures · 2025

Revenue
NOK 829,000
Operating profit
NOK 597,000
Equity
NOK 4.7m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns SMIDESANG EIENDOM AS?

ALF TORE SMIDESANG
SMIDESANG EIENDOM AS
NOK 829,000 rev. · NOK 597,000 profit

SMIDESANG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMIDESANG EIENDOM AS

Who owns SMIDESANG EIENDOM AS?

ALF TORE SMIDESANG is the largest registered owner, with 100.0%.

What is the revenue of SMIDESANG EIENDOM AS?

SMIDESANG EIENDOM AS had revenue of NOK 829,000 in 2025.

Who is the general manager of SMIDESANG EIENDOM AS?

Alf Tore Smidesang is registered as general manager of SMIDESANG EIENDOM AS.

Where is SMIDESANG EIENDOM AS based?

SMIDESANG EIENDOM AS has its business address in Lillehammer.

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.