BIZTRAC BETA
Raising of sheep

BORGAR RYGG AS

Org. no. 918538704 Limited company (AS) Luster Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 330,000
Operating profit NOK −640,000
Equity NOK 1.1m
Incorporated 2017
Share capital NOK 100,000

Signals

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

BORGAR RYGG AS is registered as a limited company in Luster, Vestland with organisation number 918538704. The business is classified under raising of sheep (NACE 01.451). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive jordbruk, sauehold med kjøttproduksjon, dyrking og vedlikehold av beiteområder, entreprenørverksemd, brøyting, kjøp og salg av anleggsmidler, samt anna verksemd som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 330,000 in revenue and NOK −640,000 in operating profit.

Key figures · 2024

Revenue
NOK 330,000
Operating profit
NOK −640,000
Equity
NOK 1.1m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns BORGAR RYGG AS?

BORGAR LUDVIGSEN RYGG
BORGAR RYGG AS
NOK 330,000 rev. · NOK −640,000 profit

BORGAR RYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGAR RYGG AS

Who owns BORGAR RYGG AS?

BORGAR LUDVIGSEN RYGG is the largest registered owner, with 100.0%.

What is the revenue of BORGAR RYGG AS?

BORGAR RYGG AS had revenue of NOK 330,000 in 2024.

Who is the general manager of BORGAR RYGG AS?

Borgar Ludvigsen Rygg is registered as general manager of BORGAR RYGG AS.

Where is BORGAR RYGG AS based?

BORGAR RYGG AS has its business address in Jostedal.

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.