biztrac. BETA
COMPANY REGISTER PROFILE
922225508 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other services incidental to land transport n.e.c.

SÆTER AUTO AS

Org. no. 922225508 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 29.6m
Operating profit NOK −1.7m
Equity NOK 3.1m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,7 mill kr).

SÆTER AUTO AS is registered as a limited company in Oslo, Oslo with organisation number 922225508. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Yte tjenester innen bilberging, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.6m in revenue and NOK −1.7m in operating profit.

Key figures · 2025

Revenue
NOK 29.6m
▼ −15 %
Operating profit
NOK −1.7m
▼ −466 %
Equity
NOK 3.1m
▼ −0 %
Est. value
NOK 15.4m

Financial health · 2025

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
-20.2%
Not satisfactory
Return on total assets
Solidity
38.2%
Good
Equity as a share of total capital

Who owns SÆTER AUTO AS?

SÆTER AUTO AS
NOK 29.6m rev. · NOK −1.7m profit

SÆTER AUTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SÆTER AUTO AS

Who owns SÆTER AUTO AS?

BJØRNEBY AS is the largest registered owner, with 100.0%.

What is the revenue of SÆTER AUTO AS?

SÆTER AUTO AS had revenue of NOK 29.6m in 2025.

Who is the general manager of SÆTER AUTO AS?

Anders Bjørneby is registered as general manager of SÆTER AUTO AS.

Where is SÆTER AUTO AS based?

SÆTER AUTO AS has its business address in Oslo.

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.