BIZTRAC BETA
Computer programming activities

LARADEV SOFTWARE AS

Org. no. 834064022 Limited company (AS) Larvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 472,000
Operating profit NOK 296,000
Equity NOK 151,000
Incorporated 2024
Share capital NOK 30,000

LARADEV SOFTWARE AS is registered as a limited company in Larvik, Vestfold with organisation number 834064022. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling, salg og implementering av programvare, samt tilby rådgivning og konsulenttjenester innenfor IT-området. Selskapet skal også kunne tilby andre tjenester som naturlig faller sammen med dette formålet.”. The most recent filed accounts, for the 2025 financial year, show NOK 472,000 in revenue and NOK 296,000 in operating profit.

Key figures · 2025

Revenue
NOK 472,000
Operating profit
NOK 296,000
Equity
NOK 151,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns LARADEV SOFTWARE AS?

LAROS AS
LARADEV SOFTWARE AS
NOK 472,000 rev. · NOK 296,000 profit

LARADEV SOFTWARE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LARADEV SOFTWARE AS

Who owns LARADEV SOFTWARE AS?

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

What is the revenue of LARADEV SOFTWARE AS?

LARADEV SOFTWARE AS had revenue of NOK 472,000 in 2025.

Who is the general manager of LARADEV SOFTWARE AS?

Christoffer Anvik Due is registered as general manager of LARADEV SOFTWARE AS.

Where is LARADEV SOFTWARE AS based?

LARADEV SOFTWARE AS has its business address in Larvik.

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.