BIZTRAC BETA
Repair and maintenance of machinery

GJESLING AS

Org. no. 933304345 Limited company (AS) Vågå Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 148,000
Operating profit NOK −481,000
Equity NOK 217,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

GJESLING AS is registered as a limited company in Vågå, Innlandet with organisation number 933304345. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby reparasjon og vedlikehold av maskiner til landbruk, skogbruk, bygg- og anlegg og industri ellers, inkludert, men ikke begrenset til, feilsøking, reparasjon, delutskifting, og andre relaterte tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 148,000 in revenue and NOK −481,000 in operating profit.

Key figures · 2025

Revenue
NOK 148,000
Operating profit
NOK −481,000
Equity
NOK 217,000
Est. value
NOK 194,000

Financial health · 2024

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

Who owns GJESLING AS?

GJESLING HOLDING AS
GJESLING AS
NOK 148,000 rev. · NOK −481,000 profit

GJESLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJESLING AS

Who owns GJESLING AS?

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

What is the revenue of GJESLING AS?

GJESLING AS had revenue of NOK 148,000 in 2025.

Who is the general manager of GJESLING AS?

Rune Gjesling Sandbo is registered as general manager of GJESLING AS.

Where is GJESLING AS based?

GJESLING AS has its business address in Vågå.

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.