biztrac. BETA
COMPANY REGISTER PROFILE
913564243 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Education at authorised driving schools

SAKSVIK TRAFIKKSKOLE AS

Org. no. 913564243 Limited company (AS) Malvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 243,000
Operating profit NOK 190,000
Equity NOK 595,000
Incorporated 2014
Share capital NOK 30,000

SAKSVIK TRAFIKKSKOLE AS is registered as a limited company in Malvik, Trøndelag with organisation number 913564243. The business is classified under education at authorised driving schools (NACE 85.531). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive trafikkskoleundervisning og det som naturlig faller inn under dette, samt administrasjon og ledelse av andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 243,000 in revenue and NOK 190,000 in operating profit.

Former names: 365 GYM AS

Key figures · 2025

Revenue
NOK 243,000
▲ +362 %
Operating profit
NOK 190,000
▲ +454 %
Equity
NOK 595,000
▲ +33 %
Est. value
NOK 678,000

Financial health · 2025

Liquidity
2.32
Very good
Current assets ÷ current liabilities
Profitability
30.4%
Very good
Return on total assets
Solidity
88.0%
Very good
Equity as a share of total capital

Who owns SAKSVIK TRAFIKKSKOLE AS?

SAKSVIK TRAFIKKSKOLE AS
NOK 243,000 rev. · NOK 190,000 profit

SAKSVIK TRAFIKKSKOLE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAKSVIK TRAFIKKSKOLE AS

Who owns SAKSVIK TRAFIKKSKOLE AS?

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

What is the revenue of SAKSVIK TRAFIKKSKOLE AS?

SAKSVIK TRAFIKKSKOLE AS had revenue of NOK 243,000 in 2025.

Where is SAKSVIK TRAFIKKSKOLE AS based?

SAKSVIK TRAFIKKSKOLE AS has its business address in Saksvik.

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.