biztrac. BETA
COMPANY REGISTER PROFILE
994901206 ORG. NO. 2017 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wired, wireless, and satellite telecommunication activities

LYCAMOBILE NORWAY LIMITED NUF

Org. no. 994901206 Norwegian division of foreign business enterprise (NUF) Oslo Active
Revenue 2017 NOK 106.6m
Operating profit NOK −1.4m
Equity NOK 0
Employees 10

Signals

1 flags
  • Driftsunderskudd 2017 Siste driftsresultat er negativt (−1,4 mill kr).

LYCAMOBILE NORWAY LIMITED NUF is registered as a norwegian division of foreign business enterprise in Oslo, Oslo with organisation number 994901206. The business is classified under wired, wireless, and satellite telecommunication activities (NACE 61.100). The company has 10 registered employees. The most recent filed accounts, for the 2017 financial year, show NOK 106.6m in revenue and NOK −1.4m in operating profit.

Former names: LYCAMOBILE NORWAY LIMITED

Key figures · 2017

Revenue
NOK 106.6m
Operating profit
NOK −1.4m
Equity
NOK 0

Financial health · 2017

Liquidity
0.31
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
0.0%
Weak
Equity as a share of total capital

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

Who owns LYCAMOBILE NORWAY LIMITED NUF?

No shareholders are registered for LYCAMOBILE NORWAY LIMITED NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LYCAMOBILE NORWAY LIMITED NUF

What is the revenue of LYCAMOBILE NORWAY LIMITED NUF?

LYCAMOBILE NORWAY LIMITED NUF had revenue of NOK 106.6m in 2017.

Who is the general manager of LYCAMOBILE NORWAY LIMITED NUF?

Vilius Danila is registered as general manager of LYCAMOBILE NORWAY LIMITED NUF.

Where is LYCAMOBILE NORWAY LIMITED NUF based?

LYCAMOBILE NORWAY LIMITED NUF has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.