BIZTRAC BETA
Wholesale of other machinery and equipment

GYLLING TEKNIKK AS

Org. no. 833858262 Limited company (AS) Bærum Incorporated 1967 Active
Ownership graph ↗
Revenue 2025 NOK 117.8m
Operating profit NOK 4.7m
Equity NOK 49.5m
Incorporated 1967
Employees 24
Share capital NOK 1.0m

GYLLING TEKNIKK AS is registered as a limited company in Bærum, Akershus with organisation number 833858262. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1967 and has 24 registered employees. Registered share capital is NOK 1.0m, divided into 200000 shares. The company's stated purpose is: “Produksjon, handel og agentur og hva som står i forbindelse med dette. Selskapet skal også kunne delta i andre selskaper med økonomisk formål samt likestilt virksomet.”. The most recent filed accounts, for the 2025 financial year, show NOK 117.8m in revenue and NOK 4.7m in operating profit.

Key figures · 2025

Revenue
NOK 117.8m
Operating profit
NOK 4.7m
Equity
NOK 49.5m
Est. value
NOK 41.8m

Financial health · 2025

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

Who owns GYLLING TEKNIKK AS?

GYLLING HOLDING AS
GYLLING TEKNIKK AS
NOK 117.8m rev. · NOK 4.7m profit

GYLLING TEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GYLLING TEKNIKK AS

Who owns GYLLING TEKNIKK AS?

GYLLING HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GYLLING TEKNIKK AS?

GYLLING TEKNIKK AS had revenue of NOK 117.8m in 2025.

Who is the general manager of GYLLING TEKNIKK AS?

Nicolai Kaas Iversen is registered as general manager of GYLLING TEKNIKK AS.

Where is GYLLING TEKNIKK AS based?

GYLLING TEKNIKK AS has its business address in Rud.

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.