biztrac. BETA
COMPANY REGISTER PROFILE
930663468 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Gambling and betting activities

BRIGHT VISION AS

Org. no. 930663468 Limited company (AS) Elverum Incorporated 2023 Active
Revenue 2025 NOK 1.1m
Operating profit NOK 14,000
Equity NOK 42,000
Incorporated 2023
Share capital NOK 30,000

BRIGHT VISION AS is registered as a limited company in Elverum, Innlandet with organisation number 930663468. The business is classified under gambling and betting activities (NACE 92.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av tjenester gjennom sport og spill og andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +64 %
Operating profit
NOK 14,000
▲ +298 %
Equity
NOK 42,000
▲ +37 %
Est. value
NOK 89,000

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
8.1%
Satisfactory
Return on total assets
Solidity
18.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BRIGHT VISION AS?

BRIGHT VISION AS
NOK 1.1m rev. · NOK 14,000 profit

BRIGHT VISION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRIGHT VISION AS

Who owns BRIGHT VISION AS?

Håkon Nerdrum is the largest registered owner, with 100.0%.

What is the revenue of BRIGHT VISION AS?

BRIGHT VISION AS had revenue of NOK 1.1m in 2025.

Who is the general manager of BRIGHT VISION AS?

Håkon Nerdrum is registered as general manager of BRIGHT VISION AS.

Where is BRIGHT VISION AS based?

BRIGHT VISION AS has its business address in Elverum.

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.