biztrac. BETA
COMPANY REGISTER PROFILE
915553273 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other content distribution activities

VENTURE ONE AS

Org. no. 915553273 Limited company (AS) Lillesand Incorporated 2015 Active
Revenue 2025 NOK 867,000
Operating profit NOK 280,000
Equity NOK 488,000
Incorporated 2015
Share capital NOK 38,000

VENTURE ONE AS is registered as a limited company in Lillesand, Agder with organisation number 915553273. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2015. Registered share capital is NOK 38,000, divided into 1265 shares. The company's stated purpose is: “Utvikling, vedlikehold og drift av web-portaler og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 867,000 in revenue and NOK 280,000 in operating profit.

Former names: A KONSULT AS, AMLIEN & GARVIK AS, FOODLINK INTERNATIONAL AS

Key figures · 2025

Revenue
NOK 867,000
▼ −15 %
Operating profit
NOK 280,000
▲ +1290 %
Equity
NOK 488,000
▲ +92 %
Est. value
NOK 901,000

Financial health · 2025

Liquidity
0.50
Weak
Current assets ÷ current liabilities
Profitability
22.3%
Very good
Return on total assets
Solidity
30.4%
Good
Equity as a share of total capital

Who owns VENTURE ONE AS?

VENTURE ONE AS
NOK 867,000 rev. · NOK 280,000 profit

VENTURE ONE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VENTURE ONE AS own?

VENTURE ONE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VENTURE ONE AS

Who owns VENTURE ONE AS?

Magnus Berglund is the largest registered owner, with 100.0%.

What is the revenue of VENTURE ONE AS?

VENTURE ONE AS had revenue of NOK 867,000 in 2025.

Where is VENTURE ONE AS based?

VENTURE ONE AS has its business address in Lillesand.

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.