BIZTRAC BETA
Rental and operating of own or leased real estate

BO COLIVING TRØNDELAG AS

Org. no. 929326199 Limited company (AS) Tønsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 23.6m
Operating profit NOK −171,000
Equity NOK 111.6m
Incorporated 2022
Employees 9
Share capital NOK 960,000

Signals

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

BO COLIVING TRØNDELAG AS is registered as a limited company in Tønsberg, Vestfold with organisation number 929326199. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022 and has 9 registered employees. Registered share capital is NOK 960,000, divided into 960159 shares. The company's stated purpose is: “Eie og drive fast eiendom, herunder utleie, samt alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.6m in revenue and NOK −171,000 in operating profit.

Key figures · 2024

Revenue
NOK 23.6m
Operating profit
NOK −171,000
Equity
NOK 111.6m
Est. value
NOK 87.5m

Financial health · 2024

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

Who owns BO COLIVING TRØNDELAG AS?

BO COLIVING AS
BO COLIVING TRØNDELAG AS
NOK 23.6m rev. · NOK −171,000 profit

BO COLIVING TRØNDELAG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BO COLIVING TRØNDELAG AS

Who owns BO COLIVING TRØNDELAG AS?

BO COLIVING AS is the largest registered owner, with 100.0%.

What is the revenue of BO COLIVING TRØNDELAG AS?

BO COLIVING TRØNDELAG AS had revenue of NOK 23.6m in 2024.

Where is BO COLIVING TRØNDELAG AS based?

BO COLIVING TRØNDELAG AS has its business address in Tønsberg.

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.