BIZTRAC BETA
Wholesale of information and communication equipment

BUYSEC AS

Org. no. 971199954 Limited company (AS) Drammen Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 30.6m
Operating profit NOK 1.3m
Equity NOK 10.4m
Incorporated 1994
Employees 11
Share capital NOK 300,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BUYSEC AS is registered as a limited company in Drammen, Buskerud with organisation number 971199954. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 1994 and has 11 registered employees. Registered share capital is NOK 300,000, divided into 1998 shares. The company's stated purpose is: “Selv eller gjennom andres selskaper, å utvikle, produsere og markedsføre sikkerhetsløsninger for informasjonssystemer, samt å yte konsulentbistand forbundet dermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 30.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 30.6m
Operating profit
NOK 1.3m
Equity
NOK 10.4m
Est. value
NOK 11.1m

Financial health · 2025

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

Who owns BUYSEC AS?

PROSERO SECURITY AS
BUYSEC AS
NOK 30.6m rev. · NOK 1.3m profit

BUYSEC AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BUYSEC AS er morselskap for 1 datterselskap:

Frequently asked questions about BUYSEC AS

Who owns BUYSEC AS?

PROSERO SECURITY AS is the largest registered owner, with 100.0%.

What is the revenue of BUYSEC AS?

BUYSEC AS had revenue of NOK 30.6m in 2025.

Where is BUYSEC AS based?

BUYSEC AS has its business address in Mjøndalen.

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.