BIZTRAC BETA
Computer consultancy and computer facilities management activities

WORK IN PROGRESS AS

Org. no. 934086260 Limited company (AS) Lindesnes Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 7,000
Equity NOK 414,000
Incorporated 2024
Share capital NOK 30,000

WORK IN PROGRESS AS is registered as a limited company in Lindesnes, Agder with organisation number 934086260. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av teknologiske tjenester, investering i selskaper og alt som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 7,000
Equity
NOK 414,000
Est. value
NOK 212,000

Financial health · 2025

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.7%
Satisfactory
Equity as a share of total capital

Who owns WORK IN PROGRESS AS?

HKJELLBY AS
WORK IN PROGRESS AS
NOK 1.3m rev. · NOK 7,000 profit

WORK IN PROGRESS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does WORK IN PROGRESS AS own?

WORK IN PROGRESS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about WORK IN PROGRESS AS

Who owns WORK IN PROGRESS AS?

HKJELLBY AS is the largest registered owner, with 50.0%.

What is the revenue of WORK IN PROGRESS AS?

WORK IN PROGRESS AS had revenue of NOK 1.3m in 2025.

Where is WORK IN PROGRESS AS based?

WORK IN PROGRESS AS has its business address in Mandal.

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.