BIZTRAC BETA
Business and other management consultancy activities

ESMAR AS

Org. no. 989175335 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 414,000
Operating profit NOK −2.0m
Equity NOK 544.2m
Incorporated 2005
Share capital NOK 2.5m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,0 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ESMAR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989175335. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 2.5m, divided into 1000000 shares. The company's stated purpose is: “Eie aksjer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 414,000 in revenue and NOK −2.0m in operating profit.

Key figures · 2024

Revenue
NOK 414,000
Operating profit
NOK −2.0m
Equity
NOK 544.2m
Est. value
NOK 1.9bn

Financial health · 2024

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

Who owns ESMAR AS?

RACCE AS
ESMAR AS
NOK 414,000 rev. · NOK −2.0m profit

ESMAR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ESMAR AS own?

ESMAR AS holds stakes in 50+ companies:

See the full ownership structure →

Group structure

ESMAR AS er morselskap for 1 datterselskap:

Frequently asked questions about ESMAR AS

Who owns ESMAR AS?

RACCE AS is the largest registered owner, with 90.0%.

What is the revenue of ESMAR AS?

ESMAR AS had revenue of NOK 414,000 in 2024.

Where is ESMAR AS based?

ESMAR AS has its business address in Trondheim.

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.