BIZTRAC BETA
Business and other management consultancy activities

LIGHTFORCE AS

Org. no. 928356833 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 49,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

LIGHTFORCE AS is registered as a limited company in Stavanger, Rogaland with organisation number 928356833. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −6,000
Equity
NOK 49,000
Est. value
NOK 79,000

Financial health · 2024

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

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

Who owns LIGHTFORCE AS?

MAIKEN EGE NILSEN
LIGHTFORCE AS
· NOK −6,000 profit

LIGHTFORCE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LIGHTFORCE AS own?

LIGHTFORCE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LIGHTFORCE AS

Who owns LIGHTFORCE AS?

MAIKEN EGE NILSEN is the largest registered owner, with 50.0%.

Who is the general manager of LIGHTFORCE AS?

Vegard Torje Haugeto is registered as general manager of LIGHTFORCE AS.

Where is LIGHTFORCE AS based?

LIGHTFORCE AS has its business address in Stavanger.

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.