BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

MEREO AS

Org. no. 982990947 Limited company (AS) Grimstad Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −40,000
Equity NOK 1.4m
Incorporated 2001
Share capital NOK 100,000

Signals

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

MEREO AS is registered as a limited company in Grimstad, Agder with organisation number 982990947. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Formidling av arbeidskraft til samarbeidende selskaper, og i den forbindelse tilhørende salg av administrasjon og konsulenttjenester, samt annen økonomisk virksomhet, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −40,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −40,000
Equity
NOK 1.4m
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns MEREO AS?

KJELL EGGE
MEREO AS
NOK 0 rev. · NOK −40,000 profit

MEREO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MEREO AS

Who owns MEREO AS?

KJELL EGGE is the largest registered owner, with 70.0%.

What is the revenue of MEREO AS?

MEREO AS had revenue of NOK 0 in 2025.

Who is the general manager of MEREO AS?

Kjell Egge is registered as general manager of MEREO AS.

Where is MEREO AS based?

MEREO 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.