BIZTRAC BETA
Graphic design and visual communication activities

EYE EYE AS

Org. no. 914770351 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK −387,000
Equity NOK 2.9m
Incorporated 2015
Share capital NOK 30,000

Signals

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

EYE EYE AS is registered as a limited company in Oslo, Oslo with organisation number 914770351. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av design-, konsulent- og IT-tjenester, utvikling av egne produkter samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK −387,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK −387,000
Equity
NOK 2.9m
Est. value
NOK 5.9m

Financial health · 2024

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

Who owns EYE EYE AS?

LIVE LØMO
EYE EYE AS
NOK 4.3m rev. · NOK −387,000 profit

EYE EYE AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EYE EYE AS own?

EYE EYE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EYE EYE AS

Who owns EYE EYE AS?

LIVE LØMO is the largest registered owner, with 33.3%.

What is the revenue of EYE EYE AS?

EYE EYE AS had revenue of NOK 4.3m in 2024.

Who is the general manager of EYE EYE AS?

Live Lømo is registered as general manager of EYE EYE AS.

Where is EYE EYE AS based?

EYE EYE AS has its business address in Oslo.

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.