BIZTRAC BETA
Other technical consultancy

LEKEPLASSHJELP AS

Org. no. 997892135 Limited company (AS) Øygarden Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 1.1m
Equity NOK 37,000
Incorporated 2012
Share capital NOK 30,000

LEKEPLASSHJELP AS is registered as a limited company in Øygarden, Vestland with organisation number 997892135. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rådgivning og hjelp til etablering og oppgraderinger av uteområder karakterisert som lekeplasser, samt sikkerhetskontroller, internkontroll, vedlikehold og drift etc av disse, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 1.1m
Equity
NOK 37,000
Est. value
NOK 3.1m

Financial health · 2025

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

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

Who owns LEKEPLASSHJELP AS?

FRANK STEINSLAND
LEKEPLASSHJELP AS
NOK 2.1m rev. · NOK 1.1m profit

LEKEPLASSHJELP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEKEPLASSHJELP AS

Who owns LEKEPLASSHJELP AS?

FRANK STEINSLAND is the largest registered owner, with 100.0%.

What is the revenue of LEKEPLASSHJELP AS?

LEKEPLASSHJELP AS had revenue of NOK 2.1m in 2025.

Who is the general manager of LEKEPLASSHJELP AS?

Frank Steinsland is registered as general manager of LEKEPLASSHJELP AS.

Where is LEKEPLASSHJELP AS based?

LEKEPLASSHJELP AS has its business address in Straume.

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.