BIZTRAC BETA
Rental and operating of own or leased real estate

SMIA UTLEIE AS

Org. no. 916340583 Limited company (AS) Eidskog Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 498,000
Operating profit NOK 15,000
Equity NOK −1.8m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,8 mill kr).

SMIA UTLEIE AS is registered as a limited company in Eidskog, Innlandet with organisation number 916340583. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive med kjøp, oppussing og utleie av eiendom og næringseiendom”. The most recent filed accounts, for the 2024 financial year, show NOK 498,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 498,000
Operating profit
NOK 15,000
Equity
NOK −1.8m
Est. value
NOK 106,000

Financial health · 2024

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-56.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SMIA UTLEIE AS?

ANDREA INGELSRUD
SMIA UTLEIE AS
NOK 498,000 rev. · NOK 15,000 profit

SMIA UTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMIA UTLEIE AS

Who owns SMIA UTLEIE AS?

ANDREA INGELSRUD is the largest registered owner, with 50.0%.

What is the revenue of SMIA UTLEIE AS?

SMIA UTLEIE AS had revenue of NOK 498,000 in 2024.

Who is the general manager of SMIA UTLEIE AS?

Michael Sigvartsen is registered as general manager of SMIA UTLEIE AS.

Where is SMIA UTLEIE AS based?

SMIA UTLEIE AS has its business address in Skotterud.

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.