BIZTRAC BETA
Computer programming activities

BIWARE AS

Org. no. 946622141 Limited company (AS) Drammen Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 59,000
Equity NOK 183,000
Incorporated 1988
Share capital NOK 100,000

BIWARE AS is registered as a limited company in Drammen, Buskerud with organisation number 946622141. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 1988. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor IT for bedrifter samt salg/formidling av dataprogram, spesielt innenfor områdende rådgivning, systemering og programutvikling. Videre skal selskapet drive med salg av program og tjenester tilknyttet mobiltelefoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 59,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 59,000
Equity
NOK 183,000
Est. value
NOK 429,000

Financial health · 2024

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

Who owns BIWARE AS?

TERJE DRAG
BIWARE AS
NOK 2.1m rev. · NOK 59,000 profit

BIWARE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BIWARE AS own?

BIWARE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BIWARE AS

Who owns BIWARE AS?

TERJE DRAG is the largest registered owner, with 50.0%.

What is the revenue of BIWARE AS?

BIWARE AS had revenue of NOK 2.1m in 2025.

Who is the general manager of BIWARE AS?

Trond Dag Eriksen is registered as general manager of BIWARE AS.

Where is BIWARE AS based?

BIWARE AS has its business address in Drammen.

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.