biztrac. BETA
COMPANY REGISTER PROFILE
915343716 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

BROKER AS

Org. no. 915343716 Limited company (AS) Oslo Incorporated 2015 Active
Revenue 2025 NOK 266.0m
Operating profit NOK 36.9m
Equity NOK 42.0m
Incorporated 2015
Employees 71
Share capital NOK 66,000

BROKER AS is registered as a limited company in Oslo, Oslo with organisation number 915343716. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2015 and has 71 registered employees. Registered share capital is NOK 66,000, divided into 500 shares. The company's stated purpose is: “Salg av datasystem, samt arbeide med utvikling innenfor samme fagfelt og eventuell deltagelse i selskap med samme teknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 266.0m in revenue and NOK 36.9m in operating profit.

Former names: WEBSYSTEMER AS, VISMA REAL ESTATE AS

Key figures · 2025

Revenue
NOK 266.0m
▲ +3 %
Operating profit
NOK 36.9m
▲ +119 %
Equity
NOK 42.0m
▲ +256 %
Est. value
NOK 218.0m

Financial health · 2025

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
33.9%
Very good
Return on total assets
Solidity
38.9%
Good
Equity as a share of total capital

Who owns BROKER AS?

NEDHALIA B.V. NL
BROKER AS
NOK 266.0m rev. · NOK 36.9m profit

BROKER AS has 1 registered shareholder:

  • NEDHALIA B.V. 100.0%
All shareholders and roles →

Frequently asked questions about BROKER AS

Who owns BROKER AS?

NEDHALIA B.V. is the largest registered owner, with 100.0%.

What is the revenue of BROKER AS?

BROKER AS had revenue of NOK 266.0m in 2025.

Who is the general manager of BROKER AS?

Hans Erik Eriksen is registered as general manager of BROKER AS.

Where is BROKER AS based?

BROKER 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 03.10.2026.

Report a problem

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