BIZTRAC BETA
Rental and operating of own or leased real estate

OFTEDAHLS AUTO AS

Org. no. 914906032 Limited company (AS) Stavanger Incorporated 1970 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK −154,000
Equity NOK 3.9m
Incorporated 1970
Share capital NOK 644,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−154k kr).

OFTEDAHLS AUTO AS is registered as a limited company in Stavanger, Rogaland with organisation number 914906032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1970. Registered share capital is NOK 644,000, divided into 230 shares. The company's stated purpose is: “Forretningsvirksomhet, herunder drift av bil- forretning, erverv og drift av eiendommer og virks omhet som er knyttet til dette, herunder erverv av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −154,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK −154,000
Equity
NOK 3.9m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns OFTEDAHLS AUTO AS?

OFTEDAHLS AUTO HOLDING AS
OFTEDAHLS AUTO AS
NOK 2.3m rev. · NOK −154,000 profit

OFTEDAHLS AUTO AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OFTEDAHLS AUTO AS er morselskap for 1 datterselskap:

Frequently asked questions about OFTEDAHLS AUTO AS

Who owns OFTEDAHLS AUTO AS?

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

What is the revenue of OFTEDAHLS AUTO AS?

OFTEDAHLS AUTO AS had revenue of NOK 2.3m in 2025.

Where is OFTEDAHLS AUTO AS based?

OFTEDAHLS AUTO AS has its business address in Stavanger.

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.