BIZTRAC BETA
Repair and maintenance of motor vehicles

BORGEDAL BILSERVICE AS

Org. no. 892897352 Limited company (AS) Ringebu Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK −1.3m
Incorporated 2008
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

BORGEDAL BILSERVICE AS is registered as a limited company in Ringebu, Innlandet with organisation number 892897352. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Vedlikehold og reparasjon av motorkjøretøyer med hovedvekt på reparasjon av biler, kjøp og salg av motorkjøretøyer samt annen type virksomhet som naturlig hører sammen med dette, herunder deltakelse i andre foretak.”.

Key figures · 2024

Operating profit
NOK −2,000
Equity
NOK −1.3m

Financial health · 2024

Liquidity
-0.90
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
211.3%
Weak
Equity as a share of total capital

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

Who owns BORGEDAL BILSERVICE AS?

OLE MARTIN BORGEDAL
BORGEDAL BILSERVICE AS
· NOK −2,000 profit

BORGEDAL BILSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGEDAL BILSERVICE AS

Who owns BORGEDAL BILSERVICE AS?

OLE MARTIN BORGEDAL is the largest registered owner, with 100.0%.

Who is the general manager of BORGEDAL BILSERVICE AS?

Ole Martin Borgedal is registered as general manager of BORGEDAL BILSERVICE AS.

Where is BORGEDAL BILSERVICE AS based?

BORGEDAL BILSERVICE AS has its business address in Fåvang.

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.