BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

OSLO TRYKKLUFT HOLDING AS

Org. no. 959812756 Limited company (AS) Nittedal Incorporated 1991 Active
Ownership graph ↗
Operating profit NOK −52,000
Equity NOK 42.6m
Incorporated 1991
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−52k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OSLO TRYKKLUFT HOLDING AS is registered as a limited company in Nittedal, Akershus with organisation number 959812756. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utleie av fast eiendom, investering i andre selskaper og eiendom og annen virksomhet som naturlig faller inn under dette.”.

Key figures · 2025

Operating profit
NOK −52,000
Equity
NOK 42.6m
Est. value
NOK 73.5m

Financial health · 2025

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

Who owns OSLO TRYKKLUFT HOLDING AS?

BJØRN NÆRUM GULBRANDSEN
OSLO TRYKKLUFT HOLDING AS
· NOK −52,000 profit

OSLO TRYKKLUFT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OSLO TRYKKLUFT HOLDING AS own?

OSLO TRYKKLUFT HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about OSLO TRYKKLUFT HOLDING AS

Who owns OSLO TRYKKLUFT HOLDING AS?

BJØRN NÆRUM GULBRANDSEN is the largest registered owner, with 100.0%.

Where is OSLO TRYKKLUFT HOLDING AS based?

OSLO TRYKKLUFT HOLDING AS has its business address in Hagan.

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.