BIZTRAC BETA
Growing of other non-perennial crops

SØRSLETT GARTNERI AS

Org. no. 979782373 Limited company (AS) Narvik Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK −1.8m
Equity NOK 566,000
Incorporated 1998
Employees 7
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,8 mill kr).

SØRSLETT GARTNERI AS is registered as a limited company in Narvik, Nordland with organisation number 979782373. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 1998 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Gartneri, hesteavl, samt annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK −1.8m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK −1.8m
Equity
NOK 566,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns SØRSLETT GARTNERI AS?

RUNE SØRSLETT
SØRSLETT GARTNERI AS
NOK 1.8m rev. · NOK −1.8m profit

SØRSLETT GARTNERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØRSLETT GARTNERI AS

Who owns SØRSLETT GARTNERI AS?

RUNE SØRSLETT is the largest registered owner, with 100.0%.

What is the revenue of SØRSLETT GARTNERI AS?

SØRSLETT GARTNERI AS had revenue of NOK 1.8m in 2024.

Who is the general manager of SØRSLETT GARTNERI AS?

Rune Sørslett is registered as general manager of SØRSLETT GARTNERI AS.

Where is SØRSLETT GARTNERI AS based?

SØRSLETT GARTNERI AS has its business address in Ballangen.

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.