BIZTRAC BETA
Activities of advertising agencies

EGGE REKLAMEBYRÅ AS

Org. no. 984048637 Limited company (AS) Lørenskog Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Operating profit NOK −8,000
Equity NOK 207,000
Incorporated 2001
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).

EGGE REKLAMEBYRÅ AS is registered as a limited company in Lørenskog, Akershus with organisation number 984048637. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Reklame- og grafisk virksomhet samt handel og hva som står i forbindelse med det samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 10,000
Operating profit
NOK −8,000
Equity
NOK 207,000
Est. value
NOK 112,000

Financial health · 2024

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

Who owns EGGE REKLAMEBYRÅ AS?

ELISABETH VIK
EGGE REKLAMEBYRÅ AS
NOK 10,000 rev. · NOK −8,000 profit

EGGE REKLAMEBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EGGE REKLAMEBYRÅ AS

Who owns EGGE REKLAMEBYRÅ AS?

ELISABETH VIK is the largest registered owner, with 100.0%.

What is the revenue of EGGE REKLAMEBYRÅ AS?

EGGE REKLAMEBYRÅ AS had revenue of NOK 10,000 in 2024.

Who is the general manager of EGGE REKLAMEBYRÅ AS?

Elisabeth Vik is registered as general manager of EGGE REKLAMEBYRÅ AS.

Where is EGGE REKLAMEBYRÅ AS based?

EGGE REKLAMEBYRÅ AS has its business address in Rasta.

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.