BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

BO OG OMSORG EIENDOM AS

Org. no. 918036806 Limited company (AS) Ringerike Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 440,000
Operating profit NOK 340,000
Equity NOK 1.5m
Incorporated 2016
Share capital NOK 700,000

BO OG OMSORG EIENDOM AS is registered as a limited company in Ringerike, Buskerud with organisation number 918036806. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2016. Registered share capital is NOK 700,000, divided into 100 shares. The company's stated purpose is: “Eiendomsinvestering og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 440,000 in revenue and NOK 340,000 in operating profit.

Key figures · 2025

Revenue
NOK 440,000
Operating profit
NOK 340,000
Equity
NOK 1.5m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns BO OG OMSORG EIENDOM AS?

ROSENHOFF EIENDOM AS
BO OG OMSORG EIENDOM AS
NOK 440,000 rev. · NOK 340,000 profit

BO OG OMSORG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BO OG OMSORG EIENDOM AS

Who owns BO OG OMSORG EIENDOM AS?

ROSENHOFF EIENDOM AS is the largest registered owner, with 75.0%.

What is the revenue of BO OG OMSORG EIENDOM AS?

BO OG OMSORG EIENDOM AS had revenue of NOK 440,000 in 2025.

Who is the general manager of BO OG OMSORG EIENDOM AS?

Nan-Ciu Chen is registered as general manager of BO OG OMSORG EIENDOM AS.

Where is BO OG OMSORG EIENDOM AS based?

BO OG OMSORG EIENDOM AS has its business address in Hønefoss.

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.