BIZTRAC BETA
Manufacture of lighting equipment

EYECATCHER LYSREKLAME AS

Org. no. 918305742 Limited company (AS) Indre Østfold Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 234,000
Equity NOK 467,000
Incorporated 2016
Share capital NOK 200,000

EYECATCHER LYSREKLAME AS is registered as a limited company in Indre Østfold, Østfold with organisation number 918305742. The business is classified under manufacture of lighting equipment (NACE 27.400). The company was incorporated in 2016. Registered share capital is NOK 200,000, divided into 4 shares. The company's stated purpose is: “Produksjon og salg av lysreklameskilt. I tillegg kommer handel med norske og utenlandske aksjer og børsnoterte og ikke børsnoterte aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 234,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK 234,000
Equity
NOK 467,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.8%
Good
Equity as a share of total capital

Who owns EYECATCHER LYSREKLAME AS?

SIGNTRONIC PRODUKTION AB
EYECATCHER LYSREKLAME AS
NOK 4.5m rev. · NOK 234,000 profit

EYECATCHER LYSREKLAME AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EYECATCHER LYSREKLAME AS

Who owns EYECATCHER LYSREKLAME AS?

SIGNTRONIC PRODUKTION AB is the largest registered owner, with 75.0%.

What is the revenue of EYECATCHER LYSREKLAME AS?

EYECATCHER LYSREKLAME AS had revenue of NOK 4.5m in 2025.

Who is the general manager of EYECATCHER LYSREKLAME AS?

Tor Arne Sletten is registered as general manager of EYECATCHER LYSREKLAME AS.

Where is EYECATCHER LYSREKLAME AS based?

EYECATCHER LYSREKLAME AS has its business address in Slitu.

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.