BIZTRAC BETA
Repair and maintenance of motor vehicles

MAGNES AUTO AS

Org. no. 987185481 Limited company (AS) Flekkefjord Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 524,000
Operating profit NOK −21,000
Equity NOK 47,000
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

MAGNES AUTO AS is registered as a limited company in Flekkefjord, Agder with organisation number 987185481. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Antirustbehandling av biler og billakkering, samt annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 524,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2024

Revenue
NOK 524,000
Operating profit
NOK −21,000
Equity
NOK 47,000
Est. value
NOK 389,000

Financial health · 2024

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MAGNES AUTO AS?

ODD MAGNE GRAM
MAGNES AUTO AS
NOK 524,000 rev. · NOK −21,000 profit

MAGNES AUTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAGNES AUTO AS

Who owns MAGNES AUTO AS?

ODD MAGNE GRAM is the largest registered owner, with 100.0%.

What is the revenue of MAGNES AUTO AS?

MAGNES AUTO AS had revenue of NOK 524,000 in 2024.

Who is the general manager of MAGNES AUTO AS?

Odd Magne Gram is registered as general manager of MAGNES AUTO AS.

Where is MAGNES AUTO AS based?

MAGNES AUTO AS has its business address in Flekkefjord.

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.