BIZTRAC BETA
Computer programming activities

BK ONCODE AS

Org. no. 918887520 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 10.8m
Operating profit NOK 516,000
Equity NOK −838,000
Incorporated 2017
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−838k kr).

BK ONCODE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 918887520. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon av nettsidersider, nettbutikker, grafisk materiell, utviklings/programmerings tjenester og databaseløsninger, salg av datautstyr og programvare og virksomhet som står i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.8m in revenue and NOK 516,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.8m
Operating profit
NOK 516,000
Equity
NOK −838,000
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-12.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BK ONCODE AS?

EMPERORHILL HOLDING AS
BK ONCODE AS
NOK 10.8m rev. · NOK 516,000 profit

BK ONCODE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BK ONCODE AS

Who owns BK ONCODE AS?

EMPERORHILL HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of BK ONCODE AS?

BK ONCODE AS had revenue of NOK 10.8m in 2025.

Where is BK ONCODE AS based?

BK ONCODE AS has its business address in Trondheim.

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.