biztrac. BETA
COMPANY REGISTER PROFILE
935257778 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

TRUZT AUTOMEGLER AS

Org. no. 935257778 Limited company (AS) Trondheim Incorporated 2025 Active
Revenue 2025 NOK 4.6m
Operating profit NOK 355,000
Equity NOK 260,000
Incorporated 2025
Share capital NOK 30,000

TRUZT AUTOMEGLER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935257778. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av bil samt enhver virksomhet som naturlig hører til under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 355,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 355,000
Equity
NOK 260,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
3.10
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
25.7%
Good
Equity as a share of total capital

Who owns TRUZT AUTOMEGLER AS?

TRUZT AUTOMEGLER AS
NOK 4.6m rev. · NOK 355,000 profit

TRUZT AUTOMEGLER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TRUZT AUTOMEGLER AS er morselskap for 1 datterselskap:

Frequently asked questions about TRUZT AUTOMEGLER AS

Who owns TRUZT AUTOMEGLER AS?

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

What is the revenue of TRUZT AUTOMEGLER AS?

TRUZT AUTOMEGLER AS had revenue of NOK 4.6m in 2025.

Who is the general manager of TRUZT AUTOMEGLER AS?

Trym Kristiansen Skogseth is registered as general manager of TRUZT AUTOMEGLER AS.

Where is TRUZT AUTOMEGLER AS based?

TRUZT AUTOMEGLER AS has its business address in Leinstrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.