biztrac. BETA
COMPANY REGISTER PROFILE
926942603 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of advertising agencies

EMERMA INVEST AS

Org. no. 926942603 Limited company (AS) Stjørdal Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −53,000
Equity NOK 566,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−53k kr).

EMERMA INVEST AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 926942603. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskap, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −53,000
▼ −44 %
Equity
NOK 566,000
▼ −7 %
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.4%
Weak
Return on total assets
Solidity
4.7%
Weak
Equity as a share of total capital

Who owns EMERMA INVEST AS?

EMERMA INVEST AS
NOK 0 rev. · NOK −53,000 profit

EMERMA INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does EMERMA INVEST AS own?

EMERMA INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about EMERMA INVEST AS

Who owns EMERMA INVEST AS?

FLAAMO HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of EMERMA INVEST AS?

EMERMA INVEST AS had revenue of NOK 0 in 2025.

Where is EMERMA INVEST AS based?

EMERMA INVEST AS has its business address in Stjørdal.

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

Report a problem

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