biztrac. BETA
COMPANY REGISTER PROFILE
934653955 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

LEAVESHILL 2 AS

Org. no. 934653955 Limited company (AS) Kristiansand Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −72,000
Equity NOK 4.9m
Incorporated 2024
Share capital NOK 381,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−72k kr).

LEAVESHILL 2 AS is registered as a limited company in Kristiansand, Agder with organisation number 934653955. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 381,000, divided into 76205 shares. The company's stated purpose is: “Utvikling, utbygging, kjøp, salg og utleie av eiendom, samt drift av fast eiendom og alt som herved står i forbindelse, herunder å delta i selskaper med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −72,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −72,000
▼ −12 %
Equity
NOK 4.9m
▼ −1 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
2588.51
Very good
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
20.4%
Good
Equity as a share of total capital

Who owns LEAVESHILL 2 AS?

LEAVESHILL 2 AS
NOK 0 rev. · NOK −72,000 profit

LEAVESHILL 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEAVESHILL 2 AS

Who owns LEAVESHILL 2 AS?

GUVI INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LEAVESHILL 2 AS?

LEAVESHILL 2 AS had revenue of NOK 0 in 2025.

Where is LEAVESHILL 2 AS based?

LEAVESHILL 2 AS has its business address in Kristiansand S.

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.