biztrac. BETA
COMPANY REGISTER PROFILE
918456368 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Pre-press and pre-media services

VELTRYKK AS

Org. no. 918456368 Limited company (AS) Moss Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 10,000
Operating profit NOK −57,000
Equity NOK 34,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

VELTRYKK AS is registered as a limited company in Moss, Østfold with organisation number 918456368. The business is classified under pre-press and pre-media services (NACE 18.130). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester innen trykksaker og IKT.”. The most recent filed accounts, for the 2025 financial year, show NOK 10,000 in revenue and NOK −57,000 in operating profit.

Key figures · 2025

Revenue
NOK 10,000
Operating profit
NOK −57,000
▼ −63 %
Equity
NOK 34,000
▼ −63 %
Est. value
NOK 23,000

Financial health · 2025

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
-48.2%
Not satisfactory
Return on total assets
Solidity
33.8%
Weak
Equity as a share of total capital

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

Who owns VELTRYKK AS?

VELTRYKK AS
NOK 10,000 rev. · NOK −57,000 profit

VELTRYKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VELTRYKK AS

Who owns VELTRYKK AS?

Paul Asgeir Stormoen is the largest registered owner, with 100.0%.

What is the revenue of VELTRYKK AS?

VELTRYKK AS had revenue of NOK 10,000 in 2025.

Who is the general manager of VELTRYKK AS?

Paul Asgeir Stormoen is registered as general manager of VELTRYKK AS.

Where is VELTRYKK AS based?

VELTRYKK AS has its business address in Dilling.

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.