BIZTRAC BETA
Other technical consultancy

TRYGG MASKIN AS

Org. no. 924436697 Limited company (AS) Vennesla Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 506,000
Equity NOK 1.4m
Incorporated 2020
Share capital NOK 30,000

TRYGG MASKIN AS is registered as a limited company in Vennesla, Agder with organisation number 924436697. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tjenester til industrien og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 506,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 506,000
Equity
NOK 1.4m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns TRYGG MASKIN AS?

JOHNNY DRANGE
TRYGG MASKIN AS
NOK 3.2m rev. · NOK 506,000 profit

TRYGG MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRYGG MASKIN AS

Who owns TRYGG MASKIN AS?

JOHNNY DRANGE is the largest registered owner, with 80.0%.

What is the revenue of TRYGG MASKIN AS?

TRYGG MASKIN AS had revenue of NOK 3.2m in 2025.

Who is the general manager of TRYGG MASKIN AS?

Johnny Drange is registered as general manager of TRYGG MASKIN AS.

Where is TRYGG MASKIN AS based?

TRYGG MASKIN AS has its business address in Vennesla.

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.