BIZTRAC BETA
Business and other management consultancy activities

BARCODE INTELLIGENCE AS

Org. no. 912371646 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 6.6m
Operating profit NOK 307,000
Equity NOK 4.6m
Incorporated 2013
Share capital NOK 30,000

BARCODE INTELLIGENCE AS is registered as a limited company in Oslo, Oslo with organisation number 912371646. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning, markedsundersøkelser, konsulentbistand, organisasjonsundersøkelser, foredragsvirksomhet, undervisning og investering.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.6m in revenue and NOK 307,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.6m
Operating profit
NOK 307,000
Equity
NOK 4.6m
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns BARCODE INTELLIGENCE AS?

PÅL SILSETH AS
BARCODE INTELLIGENCE AS
NOK 6.6m rev. · NOK 307,000 profit

BARCODE INTELLIGENCE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BARCODE INTELLIGENCE AS

Who owns BARCODE INTELLIGENCE AS?

PÅL SILSETH AS is the largest registered owner, with 36.8%.

What is the revenue of BARCODE INTELLIGENCE AS?

BARCODE INTELLIGENCE AS had revenue of NOK 6.6m in 2025.

Who is the general manager of BARCODE INTELLIGENCE AS?

Hans Petter Wøien is registered as general manager of BARCODE INTELLIGENCE AS.

Where is BARCODE INTELLIGENCE AS based?

BARCODE INTELLIGENCE AS has its business address in Oslo.

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.