BIZTRAC BETA
Computer consultancy and computer facilities management activities

WIZRD SOLUTIONS AS

Org. no. 932165430 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 762,000
Equity NOK 1.2m
Incorporated 2023
Share capital NOK 30,000

WIZRD SOLUTIONS AS is registered as a limited company in Bergen, Vestland with organisation number 932165430. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 762,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 762,000
Equity
NOK 1.2m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns WIZRD SOLUTIONS AS?

BIRKELAND KAPITAL AS
WIZRD SOLUTIONS AS
NOK 5.0m rev. · NOK 762,000 profit

WIZRD SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WIZRD SOLUTIONS AS

Who owns WIZRD SOLUTIONS AS?

BIRKELAND KAPITAL AS is the largest registered owner, with 100.0%.

What is the revenue of WIZRD SOLUTIONS AS?

WIZRD SOLUTIONS AS had revenue of NOK 5.0m in 2025.

Who is the general manager of WIZRD SOLUTIONS AS?

Martin Birkeland is registered as general manager of WIZRD SOLUTIONS AS.

Where is WIZRD SOLUTIONS AS based?

WIZRD SOLUTIONS AS has its business address in Bergen.

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.