BIZTRAC BETA
Computer programming activities

ALBICORE AS

Org. no. 999056210 Limited company (AS) Lørenskog Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 997,000
Equity NOK 254,000
Incorporated 2012
Employees 5
Share capital NOK 60,000

ALBICORE AS is registered as a limited company in Lørenskog, Akershus with organisation number 999056210. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Fremstilling/salg av IKT-Konsulenttjenester 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 3.2m in revenue and NOK 997,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 997,000
Equity
NOK 254,000
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns ALBICORE AS?

OLE GUNNAR WESTGAARD
ALBICORE AS
NOK 3.2m rev. · NOK 997,000 profit

ALBICORE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ALBICORE AS

Who owns ALBICORE AS?

OLE GUNNAR WESTGAARD is the largest registered owner, with 50.1%.

What is the revenue of ALBICORE AS?

ALBICORE AS had revenue of NOK 3.2m in 2025.

Who is the general manager of ALBICORE AS?

Ole Gunnar Westgaard is registered as general manager of ALBICORE AS.

Where is ALBICORE AS based?

ALBICORE AS has its business address in Lørenskog.

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.