BIZTRAC BETA
Activities of advertising agencies

UNIMERKING AS

Org. no. 934402324 Limited company (AS) Grimstad Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 799,000
Operating profit NOK −247,000
Equity NOK 42,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

UNIMERKING AS is registered as a limited company in Grimstad, Agder with organisation number 934402324. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg og montering av produkter innen skilt, foliering og diverse innen universell utforming.”. The most recent filed accounts, for the 2025 financial year, show NOK 799,000 in revenue and NOK −247,000 in operating profit.

Key figures · 2025

Revenue
NOK 799,000
Operating profit
NOK −247,000
Equity
NOK 42,000
Est. value
NOK 859,000

Financial health · 2025

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns UNIMERKING AS?

RUBEN ANDRÉ HANO EVJU
UNIMERKING AS
NOK 799,000 rev. · NOK −247,000 profit

UNIMERKING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about UNIMERKING AS

Who owns UNIMERKING AS?

RUBEN ANDRÉ HANO EVJU is the largest registered owner, with 50.0%.

What is the revenue of UNIMERKING AS?

UNIMERKING AS had revenue of NOK 799,000 in 2025.

Who is the general manager of UNIMERKING AS?

Ruben André Hano Evju is registered as general manager of UNIMERKING AS.

Where is UNIMERKING AS based?

UNIMERKING AS has its business address in Grimstad.

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.