BIZTRAC BETA
Rental and operating of own or leased real estate

NORSK BOLIGSERVICE AS

Org. no. 927565048 Limited company (AS) Kvinnherad Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −524,000
Equity NOK −477,000
Incorporated 2021
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−477k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−524k kr).

NORSK BOLIGSERVICE AS is registered as a limited company in Kvinnherad, Vestland with organisation number 927565048. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Kjøp salg, oppussing og utleie av fast einedom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −524,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −524,000
Equity
NOK −477,000

Financial health · 2025

Liquidity
6.64
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.9%
Weak
Equity as a share of total capital

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

Who owns NORSK BOLIGSERVICE AS?

FAS INVESTERING AS
NORSK BOLIGSERVICE AS
NOK 1.3m rev. · NOK −524,000 profit

NORSK BOLIGSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORSK BOLIGSERVICE AS

Who owns NORSK BOLIGSERVICE AS?

FAS INVESTERING AS is the largest registered owner, with 50.0%.

What is the revenue of NORSK BOLIGSERVICE AS?

NORSK BOLIGSERVICE AS had revenue of NOK 1.3m in 2025.

Where is NORSK BOLIGSERVICE AS based?

NORSK BOLIGSERVICE AS has its business address in Halsnøy Kloster.

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.