BIZTRAC BETA
Wholesale of other machinery and equipment

EANOR AS

Org. no. 927615282 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 3.8m
Equity NOK 7.3m
Incorporated 2021
Share capital NOK 220,000

Signals

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

EANOR AS is registered as a limited company in Bergen, Vestland with organisation number 927615282. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2021. Registered share capital is NOK 220,000, divided into 2000 shares. The company's stated purpose is: “Import, produksjon og salg av strømforsyningsaggregater, UPS, batterisystemer og hva dermed står i forbindelse, samt installasjon, service og rådgivning. I tillegg investeringer i andre selskaper, verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 3.8m in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 3.8m
Equity
NOK 7.3m
Est. value
NOK 17.1m

Financial health · 2024

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

Who owns EANOR AS?

BOS POWER AS
EANOR AS
NOK 5.3m rev. · NOK 3.8m profit

EANOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EANOR AS

Who owns EANOR AS?

BOS POWER AS is the largest registered owner, with 100.0%.

What is the revenue of EANOR AS?

EANOR AS had revenue of NOK 5.3m in 2024.

Who is the general manager of EANOR AS?

Arild Jensen is registered as general manager of EANOR AS.

Where is EANOR AS based?

EANOR AS has its business address in Laksevåg.

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.