BIZTRAC BETA
Freight ocean transport

2020 BULKERS SAO PAULO AS

Org. no. 928949575 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 105.4m
Operating profit NOK 60.9m
Equity NOK 1.6m
Incorporated 2022
Share capital NOK 90,000

Signals

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

2020 BULKERS SAO PAULO AS is registered as a limited company in Oslo, Oslo with organisation number 928949575. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2022. Registered share capital is NOK 90,000, divided into 30000 shares. The company's stated purpose is: “Å eie, leie eller på andre måter disponere over skip, for utleie eller egen drift, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 105.4m in revenue and NOK 60.9m in operating profit.

Key figures · 2025

Revenue
NOK 105.4m
Operating profit
NOK 60.9m
Equity
NOK 1.6m
Est. value
NOK 157.3m

Financial health · 2025

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.4%
Not satisfactory
Equity as a share of total capital

Who owns 2020 BULKERS SAO PAULO AS?

2020 BULKERS LTD. NUF
2020 BULKERS SAO PAULO AS
NOK 105.4m rev. · NOK 60.9m profit

2020 BULKERS SAO PAULO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 2020 BULKERS SAO PAULO AS

Who owns 2020 BULKERS SAO PAULO AS?

2020 BULKERS LTD. NUF is the largest registered owner, with 100.0%.

What is the revenue of 2020 BULKERS SAO PAULO AS?

2020 BULKERS SAO PAULO AS had revenue of NOK 105.4m in 2025.

Where is 2020 BULKERS SAO PAULO AS based?

2020 BULKERS SAO PAULO AS has its business address in Oslo.

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.