BIZTRAC BETA
Rental and operating of own or leased real estate

HOLBÆK UTLEIE AS

Org. no. 925000876 Limited company (AS) Vennesla Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 340,000
Operating profit NOK 107,000
Equity NOK 599,000
Incorporated 2020
Share capital NOK 46,000

Signals

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

HOLBÆK UTLEIE AS is registered as a limited company in Vennesla, Agder with organisation number 925000876. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 46,000, divided into 23 shares. The company's stated purpose is: “Eie, utvikle, bygge ut og leie ut fast eiendom og å eie og leie ut faste og flyttbare installasjoner, herunder delta i andre selskaper som aksjeeier og/eller selskapsdeltaker.”. The most recent filed accounts, for the 2024 financial year, show NOK 340,000 in revenue and NOK 107,000 in operating profit.

Key figures · 2024

Revenue
NOK 340,000
Operating profit
NOK 107,000
Equity
NOK 599,000
Est. value
NOK 442,000

Financial health · 2024

Liquidity
4.01
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.8%
Satisfactory
Equity as a share of total capital

Who owns HOLBÆK UTLEIE AS?

HOLBÆK HOLDING AS
HOLBÆK UTLEIE AS
NOK 340,000 rev. · NOK 107,000 profit

HOLBÆK UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLBÆK UTLEIE AS

Who owns HOLBÆK UTLEIE AS?

HOLBÆK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HOLBÆK UTLEIE AS?

HOLBÆK UTLEIE AS had revenue of NOK 340,000 in 2024.

Where is HOLBÆK UTLEIE AS based?

HOLBÆK UTLEIE AS has its business address in Vennesla.

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.