BIZTRAC BETA
Other printing

GAUSDAL TRYKKERI AS

Org. no. 943823049 Limited company (AS) Lillehammer Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 25,000
Operating profit NOK −22,000
Equity NOK 1.1m
Incorporated 1987
Share capital NOK 100,000

Signals

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

GAUSDAL TRYKKERI AS is registered as a limited company in Lillehammer, Innlandet with organisation number 943823049. The business is classified under other printing (NACE 18.120). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Trykkerivirksomhet og hva hermed står i forbin- delse, samt ved aksjetegning eller på annen måte gjøre seg interessert i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 25,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 25,000
Operating profit
NOK −22,000
Equity
NOK 1.1m
Est. value
NOK 588,000

Financial health · 2025

Liquidity
188.67
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns GAUSDAL TRYKKERI AS?

ARNE WOLD
GAUSDAL TRYKKERI AS
NOK 25,000 rev. · NOK −22,000 profit

GAUSDAL TRYKKERI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GAUSDAL TRYKKERI AS own?

GAUSDAL TRYKKERI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GAUSDAL TRYKKERI AS

Who owns GAUSDAL TRYKKERI AS?

ARNE WOLD is the largest registered owner, with 100.0%.

What is the revenue of GAUSDAL TRYKKERI AS?

GAUSDAL TRYKKERI AS had revenue of NOK 25,000 in 2025.

Where is GAUSDAL TRYKKERI AS based?

GAUSDAL TRYKKERI AS has its business address in Lillehammer.

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.