BIZTRAC BETA
Rental and operating of own or leased real estate

TRYKKERIGÅRDEN AS

Org. no. 973052365 Limited company (AS) Stavanger Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 2.6m
Equity NOK 13.9m
Incorporated 1995
Share capital NOK 300,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRYKKERIGÅRDEN AS is registered as a limited company in Stavanger, Rogaland with organisation number 973052365. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1995. Registered share capital is NOK 300,000. The company's stated purpose is: “Drift av fast eiendom og hva dermed står i forbindelse herunder kjøp/salg fast eiendom og aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 2.6m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 2.6m
Equity
NOK 13.9m
Est. value
NOK 15.5m

Financial health · 2025

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

Who owns TRYKKERIGÅRDEN AS?

ELTO FINANS AS
TRYKKERIGÅRDEN AS
NOK 3.0m rev. · NOK 2.6m profit

TRYKKERIGÅRDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYKKERIGÅRDEN AS

Who owns TRYKKERIGÅRDEN AS?

ELTO FINANS AS is the largest registered owner, with 100.0%.

What is the revenue of TRYKKERIGÅRDEN AS?

TRYKKERIGÅRDEN AS had revenue of NOK 3.0m in 2025.

Who is the general manager of TRYKKERIGÅRDEN AS?

Torfinn Eddy Hansen is registered as general manager of TRYKKERIGÅRDEN AS.

Where is TRYKKERIGÅRDEN AS based?

TRYKKERIGÅRDEN AS has its business address in Stavanger.

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.