BIZTRAC BETA
Graphic design and visual communication activities

VISTORY NORGE AS

Org. no. 932557525 Limited company (AS) Ås Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −199
Equity NOK 18,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−199 kr).

VISTORY NORGE AS is registered as a limited company in Ås, Akershus with organisation number 932557525. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon og salg av tjenester innenfor grafisk og foto virksomhet, administrativ rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −199 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −199
Equity
NOK 18,000
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns VISTORY NORGE AS?

LUU-HUYNH HOLDING AS
VISTORY NORGE AS
NOK 0 rev. · NOK −199 profit

VISTORY NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VISTORY NORGE AS

Who owns VISTORY NORGE AS?

LUU-HUYNH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VISTORY NORGE AS?

VISTORY NORGE AS had revenue of NOK 0 in 2025.

Who is the general manager of VISTORY NORGE AS?

Daniel Tran Huynh is registered as general manager of VISTORY NORGE AS.

Where is VISTORY NORGE AS based?

VISTORY NORGE AS has its business address in Ås.

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.