BIZTRAC BETA
Graphic design and visual communication activities

EDDA GRAFISK AS

Org. no. 926950789 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK −136,000
Equity NOK −54,000
Incorporated 2021
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−54k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−136k kr).

EDDA GRAFISK AS is registered as a limited company in Bærum, Akershus with organisation number 926950789. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 2000 shares. The company's stated purpose is: “Publisistisk virksomhet, herunder trykkformidling og grafisk design og utarbeidelse av produksjons-filer til magasiner og aviser, samt design av nettsteder/publikasjoner.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK −136,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK −136,000
Equity
NOK −54,000

Financial health · 2024

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-10.6%
Weak
Equity as a share of total capital

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

Who owns EDDA GRAFISK AS?

BERGSTRØM AS
EDDA GRAFISK AS
NOK 3.2m rev. · NOK −136,000 profit

EDDA GRAFISK AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about EDDA GRAFISK AS

Who owns EDDA GRAFISK AS?

BERGSTRØM AS is the largest registered owner, with 30.0%.

What is the revenue of EDDA GRAFISK AS?

EDDA GRAFISK AS had revenue of NOK 3.2m in 2024.

Where is EDDA GRAFISK AS based?

EDDA GRAFISK AS has its business address in Lysaker.

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.