BIZTRAC BETA
Retail sale of articles for lighting

FIBEROPTISK LYS CALCO AS

Org. no. 970979085 Limited company (AS) Risør Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 1.3m
Equity NOK 3.4m
Incorporated 1994
Share capital NOK 100,000

FIBEROPTISK LYS CALCO AS is registered as a limited company in Risør, Agder with organisation number 970979085. The business is classified under retail sale of articles for lighting (NACE 47.552). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel, import, eksport, fiberoptisk beslysning, utleie, konsulentvirksmhet, fast eiendom samt deltakelse i andre selskaper og hva som derved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 1.3m
Equity
NOK 3.4m
Est. value
NOK 6.2m

Financial health · 2025

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

Who owns FIBEROPTISK LYS CALCO AS?

PER RØDHALL
FIBEROPTISK LYS CALCO AS
NOK 3.0m rev. · NOK 1.3m profit

FIBEROPTISK LYS CALCO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FIBEROPTISK LYS CALCO AS

Who owns FIBEROPTISK LYS CALCO AS?

PER RØDHALL is the largest registered owner, with 75.0%.

What is the revenue of FIBEROPTISK LYS CALCO AS?

FIBEROPTISK LYS CALCO AS had revenue of NOK 3.0m in 2025.

Who is the general manager of FIBEROPTISK LYS CALCO AS?

Per Rødhall is registered as general manager of FIBEROPTISK LYS CALCO AS.

Where is FIBEROPTISK LYS CALCO AS based?

FIBEROPTISK LYS CALCO AS has its business address in Risør.

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.