biztrac. BETA
COMPANY REGISTER PROFILE
931930451 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

BEVER CONTROL AS

Org. no. 931930451 Limited company (AS) Lier Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 46.0m
Operating profit NOK 8.2m
Equity NOK 23.8m
Incorporated 1982
Employees 18
Share capital NOK 6.0m

BEVER CONTROL AS is registered as a limited company in Lier, Buskerud with organisation number 931930451. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 1982 and has 18 registered employees. Registered share capital is NOK 6.0m, divided into 600000 shares. The company's stated purpose is: “Å drive industriell utvikling, produksjon og markedsføring, samt hva som derunder står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 46.0m in revenue and NOK 8.2m in operating profit.

Key figures · 2025

Revenue
NOK 46.0m
▼ −18 %
Operating profit
NOK 8.2m
▼ −39 %
Equity
NOK 23.8m
▼ −14 %
Est. value
NOK 63.7m

Financial health · 2025

Liquidity
1.86
Good
Current assets ÷ current liabilities
Profitability
19.9%
Very good
Return on total assets
Solidity
47.7%
Very good
Equity as a share of total capital

Who owns BEVER CONTROL AS?

BEVER CONTROL AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about BEVER CONTROL AS

Who owns BEVER CONTROL AS?

JANIX IKT AS is the largest registered owner, with 20.2%.

What is the revenue of BEVER CONTROL AS?

BEVER CONTROL AS had revenue of NOK 46.0m in 2025.

Who is the general manager of BEVER CONTROL AS?

Thorvald Bjørnstad Wetlesen is registered as general manager of BEVER CONTROL AS.

Where is BEVER CONTROL AS based?

BEVER CONTROL AS has its business address in Lierskogen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.