BIZTRAC BETA
Business and other management consultancy activities

STEINGARDEN AS

Org. no. 820469402 Limited company (AS) Klepp Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 180,000
Operating profit NOK 21,000
Equity NOK 4.6m
Incorporated 2018
Share capital NOK 60,000

STEINGARDEN AS is registered as a limited company in Klepp, Rogaland with organisation number 820469402. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Bedriftsrådgivning samt det som naturlig står i forbindelse med dette herunder investering og deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 180,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2025

Revenue
NOK 180,000
Operating profit
NOK 21,000
Equity
NOK 4.6m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns STEINGARDEN AS?

JOHN LENDE
STEINGARDEN AS
NOK 180,000 rev. · NOK 21,000 profit

STEINGARDEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STEINGARDEN AS own?

STEINGARDEN AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about STEINGARDEN AS

Who owns STEINGARDEN AS?

JOHN LENDE is the largest registered owner, with 70.0%.

What is the revenue of STEINGARDEN AS?

STEINGARDEN AS had revenue of NOK 180,000 in 2025.

Who is the general manager of STEINGARDEN AS?

Marion Lende is registered as general manager of STEINGARDEN AS.

Where is STEINGARDEN AS based?

STEINGARDEN AS has its business address in Klepp Stasjon.

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.