BIZTRAC BETA
Other printing

BIAS TRYKK AS

Org. no. 975901211 Limited company (AS) Oslo Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 451,000
Operating profit NOK −35,000
Equity NOK 37,000
Incorporated 1995
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−35k kr).

BIAS TRYKK AS is registered as a limited company in Oslo, Oslo with organisation number 975901211. The business is classified under other printing (NACE 18.120). The company was incorporated in 1995. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Grafisk virksomhet, investere og forvalte eiendom og aksjer og det som herved står i forbindelse, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 451,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2024

Revenue
NOK 451,000
Operating profit
NOK −35,000
Equity
NOK 37,000
Est. value
NOK 262,000

Financial health · 2024

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

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

Who owns BIAS TRYKK AS?

SIGURD EDVARD ASPDAHL
BIAS TRYKK AS
NOK 451,000 rev. · NOK −35,000 profit

BIAS TRYKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIAS TRYKK AS

Who owns BIAS TRYKK AS?

SIGURD EDVARD ASPDAHL is the largest registered owner, with 100.0%.

What is the revenue of BIAS TRYKK AS?

BIAS TRYKK AS had revenue of NOK 451,000 in 2024.

Who is the general manager of BIAS TRYKK AS?

Sigurd Edvard Aspdahl is registered as general manager of BIAS TRYKK AS.

Where is BIAS TRYKK AS based?

BIAS TRYKK AS has its business address in Oslo.

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.