BIZTRAC BETA
COMPANY REGISTER PROFILE
928122646 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Freight ocean transport

BRIESE ECO HANDY AS

Org. no. 928122646 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Equity NOK 90.0m
Incorporated 2021
Share capital NOK 1.1m

BRIESE ECO HANDY AS is registered as a limited company in Oslo, Oslo with organisation number 928122646. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2021. Registered share capital is NOK 1.1m, divided into 1000000 shares. The company's stated purpose is: “Drive skipsfart og rederivirksomhet, samt hva som hermed står i forbindelse, herunder deltakelse i andre selskaper med tilsvarende formål.”.

Former names: VIOS 229 AS

Key figures · 2025

Equity
NOK 90.0m
▼ −0 %
Est. value
NOK 87.8m

Financial health · 2025

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

Who owns BRIESE ECO HANDY AS?

BRIESE ECO HANDY AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about BRIESE ECO HANDY AS

Who owns BRIESE ECO HANDY AS?

OLOF BRODIN (DRYBULK) AB is the largest registered owner, with 20.0%.

Where is BRIESE ECO HANDY AS based?

BRIESE ECO HANDY AS has its business address in Oslo.

Property

Business address c/o NRP Business Management AS Drammensveien 88B, 0271 Oslo
Cadastral unit 301-212/122/0/0
Building Annen kontorbygning · 1 unit

116 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.