biztrac. BETA
COMPANY REGISTER PROFILE
935142180 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of fitness centres

LAGER 4 AS

Org. no. 935142180 Limited company (AS) Vennesla Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 153,000
Operating profit NOK −10,000
Equity NOK −7,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

LAGER 4 AS is registered as a limited company in Vennesla, Agder with organisation number 935142180. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Treningssenter og golfsimulator, samt deltakelse i andre tilsvarende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 153,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 153,000
Operating profit
NOK −10,000
Equity
NOK −7,000

Financial health · 2025

Liquidity
-128.52
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-0.3%
Weak
Equity as a share of total capital

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

Who owns LAGER 4 AS?

LAGER 4 AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAGER 4 AS

Who owns LAGER 4 AS?

Birgitte Lindekleiv Svaland is the largest registered owner, with 16.7%.

What is the revenue of LAGER 4 AS?

LAGER 4 AS had revenue of NOK 153,000 in 2025.

Who is the general manager of LAGER 4 AS?

Simon Ellingsberg is registered as general manager of LAGER 4 AS.

Where is LAGER 4 AS based?

LAGER 4 AS has its business address in Hægeland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.