BIZTRAC BETA
Rental and operating of own or leased real estate

SIS UTLEIE AS

Org. no. 981225368 Limited company (AS) Gol Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 91,000
Operating profit NOK −9,000
Equity NOK 473,000
Incorporated 1999
Share capital NOK 195,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

SIS UTLEIE AS is registered as a limited company in Gol, Buskerud with organisation number 981225368. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 195,000, divided into 195 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom. Utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 91,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 91,000
Operating profit
NOK −9,000
Equity
NOK 473,000
Est. value
NOK 461,000

Financial health · 2025

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

Who owns SIS UTLEIE AS?

SVEIN HAUGSTAD
SIS UTLEIE AS
NOK 91,000 rev. · NOK −9,000 profit

SIS UTLEIE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SIS UTLEIE AS own?

SIS UTLEIE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIS UTLEIE AS

Who owns SIS UTLEIE AS?

SVEIN HAUGSTAD is the largest registered owner, with 33.3%.

What is the revenue of SIS UTLEIE AS?

SIS UTLEIE AS had revenue of NOK 91,000 in 2025.

Who is the general manager of SIS UTLEIE AS?

Svein Haugstad is registered as general manager of SIS UTLEIE AS.

Where is SIS UTLEIE AS based?

SIS UTLEIE AS has its business address in Gol.

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.