BIZTRAC BETA
Computer consultancy and computer facilities management activities

LUCAMA AS

Org. no. 927057409 Limited company (AS) Sandefjord Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 300,000
Operating profit NOK 227,000
Equity NOK 7.3m
Incorporated 2021
Share capital NOK 30,000

LUCAMA AS is registered as a limited company in Sandefjord, Vestfold with organisation number 927057409. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenesteytende virksomhet innen telekom. Virksomheten kan også drives ved deltagelse i eller i samarbeid med andre foretagender, investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 300,000 in revenue and NOK 227,000 in operating profit.

Key figures · 2025

Revenue
NOK 300,000
Operating profit
NOK 227,000
Equity
NOK 7.3m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns LUCAMA AS?

THOMAS NORLIN HOFSTEDT
LUCAMA AS
NOK 300,000 rev. · NOK 227,000 profit

LUCAMA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUCAMA AS own?

LUCAMA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LUCAMA AS

Who owns LUCAMA AS?

THOMAS NORLIN HOFSTEDT is the largest registered owner, with 100.0%.

What is the revenue of LUCAMA AS?

LUCAMA AS had revenue of NOK 300,000 in 2025.

Where is LUCAMA AS based?

LUCAMA AS has its business address in Sandefjord.

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.