BIZTRAC BETA
Site preparation

BOJO SHIPPING AS

Org. no. 912108368 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 379,000
Incorporated 2013
Share capital NOK 220,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-05-04 Adresseendring registrert 2026-05-04.

BOJO SHIPPING AS is registered as a limited company in Bærum, Akershus with organisation number 912108368. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2013. Registered share capital is NOK 220,000, divided into 1100000 shares. The company's stated purpose is: “Å utvikle og investere i skipsfart og relatert virksomhet, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 379,000
Est. value
NOK 388,000

Financial health · 2024

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

Who owns BOJO SHIPPING AS?

BOJO INDUSTRIES AS
BOJO SHIPPING AS
NOK 0 rev. · NOK 0 profit

BOJO SHIPPING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOJO SHIPPING AS

Who owns BOJO SHIPPING AS?

BOJO INDUSTRIES AS is the largest registered owner, with 90.2%.

What is the revenue of BOJO SHIPPING AS?

BOJO SHIPPING AS had revenue of NOK 0 in 2024.

Where is BOJO SHIPPING AS based?

BOJO SHIPPING AS has its business address in Snarøya.

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.