BIZTRAC BETA
Rental and operating of own or leased real estate

VALUE BOLIGSERVICE AS

Org. no. 912794474 Limited company (AS) Skien Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 18.0m
Operating profit NOK 11.6m
Equity NOK 10.3m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VALUE BOLIGSERVICE AS is registered as a limited company in Skien, Telemark with organisation number 912794474. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å driver med investerng i eiendom, utleie av eiendommer og det som står i naturlig forbindelse med dette, herunder deltakelse i andre foretak med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.0m in revenue and NOK 11.6m in operating profit.

Key figures · 2024

Revenue
NOK 18.0m
Operating profit
NOK 11.6m
Equity
NOK 10.3m
Est. value
NOK 22.5m

Financial health · 2024

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

Who owns VALUE BOLIGSERVICE AS?

BAKKEDAMMEN AS
VALUE BOLIGSERVICE AS
NOK 18.0m rev. · NOK 11.6m profit

VALUE BOLIGSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VALUE BOLIGSERVICE AS

Who owns VALUE BOLIGSERVICE AS?

BAKKEDAMMEN AS is the largest registered owner, with 51.0%.

What is the revenue of VALUE BOLIGSERVICE AS?

VALUE BOLIGSERVICE AS had revenue of NOK 18.0m in 2024.

Where is VALUE BOLIGSERVICE AS based?

VALUE BOLIGSERVICE AS has its business address in Skien.

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.