BIZTRAC BETA
Computer programming activities

PRIMROSE AS

Org. no. 987995467 Limited company (AS) Lillesand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 335,000
Equity NOK 417,000
Incorporated 2005
Share capital NOK 200,000

PRIMROSE AS is registered as a limited company in Lillesand, Agder with organisation number 987995467. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 600 shares. The company's stated purpose is: “Fremstilling/salg av dataprogrammer, konsulentvirksomhet innen EDB, samt handel med EDB-relaterte produkter og andre produkter 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 foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 335,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 335,000
Equity
NOK 417,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns PRIMROSE AS?

JAN GUNNAR MJÅLAND
PRIMROSE AS
NOK 2.1m rev. · NOK 335,000 profit

PRIMROSE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRIMROSE AS

Who owns PRIMROSE AS?

JAN GUNNAR MJÅLAND is the largest registered owner, with 50.0%.

What is the revenue of PRIMROSE AS?

PRIMROSE AS had revenue of NOK 2.1m in 2025.

Who is the general manager of PRIMROSE AS?

Bjarne Harbo Galteland is registered as general manager of PRIMROSE AS.

Where is PRIMROSE AS based?

PRIMROSE AS has its business address in Lillesand.

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.