BIZTRAC BETA
Architectural activities

BO ARKITEKTER AS

Org. no. 985696241 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 860,000
Operating profit NOK 50,000
Equity NOK −364,000
Incorporated 2003
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−364k kr).

BO ARKITEKTER AS is registered as a limited company in Bergen, Vestland with organisation number 985696241. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Arkiteksvirksomhet og her til andre tjenester som naturlig hører inn under denne type virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 860,000 in revenue and NOK 50,000 in operating profit.

Key figures · 2025

Revenue
NOK 860,000
Operating profit
NOK 50,000
Equity
NOK −364,000
Est. value
NOK 267,000

Financial health · 2025

Liquidity
0.84
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-102.1%
Weak
Equity as a share of total capital

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

Who owns BO ARKITEKTER AS?

KLAUS BO CHRISTENSEN
BO ARKITEKTER AS
NOK 860,000 rev. · NOK 50,000 profit

BO ARKITEKTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BO ARKITEKTER AS

Who owns BO ARKITEKTER AS?

KLAUS BO CHRISTENSEN is the largest registered owner, with 50.0%.

What is the revenue of BO ARKITEKTER AS?

BO ARKITEKTER AS had revenue of NOK 860,000 in 2025.

Who is the general manager of BO ARKITEKTER AS?

Klaus Bo Christensen is registered as general manager of BO ARKITEKTER AS.

Where is BO ARKITEKTER AS based?

BO ARKITEKTER AS has its business address in Fana.

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.