BIZTRAC BETA
Computer programming activities

LOREBOUND AS

Org. no. 930687723 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 89,000
Operating profit NOK −1.4m
Equity NOK −1.8m
Incorporated 2023
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,8 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

LOREBOUND AS is registered as a limited company in Drammen, Buskerud with organisation number 930687723. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Utvikle, markedsføre og selge dataspill, samt beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 89,000 in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 89,000
Operating profit
NOK −1.4m
Equity
NOK −1.8m

Financial health · 2024

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

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

Who owns LOREBOUND AS?

EIRIK WIKLUND AS
LOREBOUND AS
NOK 89,000 rev. · NOK −1.4m profit

LOREBOUND AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOREBOUND AS

Who owns LOREBOUND AS?

EIRIK WIKLUND AS is the largest registered owner, with 50.0%.

What is the revenue of LOREBOUND AS?

LOREBOUND AS had revenue of NOK 89,000 in 2024.

Who is the general manager of LOREBOUND AS?

Eirik Wiklund is registered as general manager of LOREBOUND AS.

Where is LOREBOUND AS based?

LOREBOUND AS has its business address in Drammen.

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.