biztrac. BETA
COMPANY REGISTER PROFILE
929751035 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

KLØVERTUNET G HJEMMEL AS

Org. no. 929751035 Limited company (AS) Oslo Incorporated 2022 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 40,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KLØVERTUNET G HJEMMEL AS is registered as a limited company in Oslo, Oslo with organisation number 929751035. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 40,000
▲ +0 %
Est. value
NOK 47,000

Financial health · 2025

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

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

Who owns KLØVERTUNET G HJEMMEL AS?

KLØVERTUNET G HJEMMEL AS
NOK 0 rev. · NOK 0 profit

KLØVERTUNET G HJEMMEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLØVERTUNET G HJEMMEL AS

Who owns KLØVERTUNET G HJEMMEL AS?

BORETTSLAGET KLØVERTUNET is the largest registered owner, with 100.0%.

What is the revenue of KLØVERTUNET G HJEMMEL AS?

KLØVERTUNET G HJEMMEL AS had revenue of NOK 0 in 2025.

Where is KLØVERTUNET G HJEMMEL AS based?

KLØVERTUNET G HJEMMEL AS has its business address in Oslo.

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.