BIZTRAC BETA
Rental and operating of own or leased real estate

SRS BOLIGUTLEIE AS

Org. no. 994538683 Limited company (AS) Overhalla Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 684,000
Operating profit NOK −170,000
Equity NOK 2.2m
Incorporated 2009
Share capital NOK 1.4m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−170k kr).

SRS BOLIGUTLEIE AS is registered as a limited company in Overhalla, Trøndelag with organisation number 994538683. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 1.4m, divided into 1350 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom. Samt å kunne delta i andre virksomheter. ”. The most recent filed accounts, for the 2024 financial year, show NOK 684,000 in revenue and NOK −170,000 in operating profit.

Key figures · 2024

Revenue
NOK 684,000
Operating profit
NOK −170,000
Equity
NOK 2.2m
Est. value
NOK 1.8m

Financial health · 2024

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.6%
Good
Equity as a share of total capital

Who owns SRS BOLIGUTLEIE AS?

KIS UTBYGGING AS
SRS BOLIGUTLEIE AS
NOK 684,000 rev. · NOK −170,000 profit

SRS BOLIGUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SRS BOLIGUTLEIE AS

Who owns SRS BOLIGUTLEIE AS?

KIS UTBYGGING AS is the largest registered owner, with 100.0%.

What is the revenue of SRS BOLIGUTLEIE AS?

SRS BOLIGUTLEIE AS had revenue of NOK 684,000 in 2024.

Who is the general manager of SRS BOLIGUTLEIE AS?

Kåre Magnus Skjefte is registered as general manager of SRS BOLIGUTLEIE AS.

Where is SRS BOLIGUTLEIE AS based?

SRS BOLIGUTLEIE AS has its business address in Skage I Namdalen.

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.