BIZTRAC BETA
Wholesale of other machinery and equipment

ECO BEARINGS AS

Org. no. 919480394 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 469,000
Operating profit NOK 248,000
Equity NOK 1.3m
Incorporated 2017
Share capital NOK 6.1m

Signals

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

ECO BEARINGS AS is registered as a limited company in Bergen, Vestland with organisation number 919480394. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2017. Registered share capital is NOK 6.1m, divided into 204082 shares. The company's stated purpose is: “Utvikling, produksjon, salg og markedsføring av produkter & tjenester til industrien, spesielt relatert til maritime kundegrupper.”. The most recent filed accounts, for the 2025 financial year, show NOK 469,000 in revenue and NOK 248,000 in operating profit.

Key figures · 2025

Revenue
NOK 469,000
Operating profit
NOK 248,000
Equity
NOK 1.3m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns ECO BEARINGS AS?

AQUILA OG SIRIUS AS
ECO BEARINGS AS
NOK 469,000 rev. · NOK 248,000 profit

ECO BEARINGS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ECO BEARINGS AS er morselskap for 3 datterselskaper:

Frequently asked questions about ECO BEARINGS AS

Who owns ECO BEARINGS AS?

AQUILA OG SIRIUS AS is the largest registered owner, with 100.0%.

What is the revenue of ECO BEARINGS AS?

ECO BEARINGS AS had revenue of NOK 469,000 in 2025.

Where is ECO BEARINGS AS based?

ECO BEARINGS AS has its business address in Paradis.

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.