BIZTRAC BETA
Other non-specialised retail sale

3V3 NORGE AS

Org. no. 917481075 Limited company (AS) Nittedal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 373,000
Equity NOK −469,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−469k kr).

3V3 NORGE AS is registered as a limited company in Nittedal, Akershus with organisation number 917481075. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Netthandel med sportsutstyr, arrangere events og turneringer, drive undervisning og markedsføring, samt investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 373,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 373,000
Equity
NOK −469,000
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-61.4%
Weak
Equity as a share of total capital

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

Who owns 3V3 NORGE AS?

FINN OVE INVEST AS
3V3 NORGE AS
NOK 3.3m rev. · NOK 373,000 profit

3V3 NORGE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about 3V3 NORGE AS

Who owns 3V3 NORGE AS?

FINN OVE INVEST AS is the largest registered owner, with 60.0%.

What is the revenue of 3V3 NORGE AS?

3V3 NORGE AS had revenue of NOK 3.3m in 2025.

Who is the general manager of 3V3 NORGE AS?

Finn Ove Søfting is registered as general manager of 3V3 NORGE AS.

Where is 3V3 NORGE AS based?

3V3 NORGE AS has its business address in Nittedal.

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.