BIZTRAC BETA
Rental and operating of own or leased real estate

CRESCERE EIENDOM AS

Org. no. 931469711 Limited company (AS) Klepp Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 136,000
Operating profit NOK 417
Equity NOK 1.2m
Incorporated 2023
Share capital NOK 100,000

Signals

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

CRESCERE EIENDOM AS is registered as a limited company in Klepp, Rogaland with organisation number 931469711. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 136,000 in revenue and NOK 417 in operating profit.

Key figures · 2025

Revenue
NOK 136,000
Operating profit
NOK 417
Equity
NOK 1.2m
Est. value
NOK 804,000

Financial health · 2025

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.8%
Good
Equity as a share of total capital

Who owns CRESCERE EIENDOM AS?

CRESCERE-HOLDING AS
CRESCERE EIENDOM AS
NOK 136,000 rev. · NOK 417 profit

CRESCERE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

CRESCERE EIENDOM AS er morselskap for 3 datterselskaper:

Frequently asked questions about CRESCERE EIENDOM AS

Who owns CRESCERE EIENDOM AS?

CRESCERE-HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of CRESCERE EIENDOM AS?

CRESCERE EIENDOM AS had revenue of NOK 136,000 in 2025.

Where is CRESCERE EIENDOM AS based?

CRESCERE EIENDOM 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.