BIZTRAC BETA
COMPANY REGISTER PROFILE
934405285 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

HT BOLIG AS

Org. no. 934405285 Limited company (AS) Vennesla Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −49,000
Equity NOK 454,000
Incorporated 2024
Share capital NOK 500,000

Signals

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

HT BOLIG AS is registered as a limited company in Vennesla, Agder with organisation number 934405285. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Oppføring og salg av boliger og alt som naturlig hører sammen med dette. Selskapet kan også investere i aksjer, andeler og andre finans- og realobjekter, samt fast eiendom.”.

Key figures · 2025

Operating profit
NOK −49,000
Equity
NOK 454,000
Est. value
NOK 415,000

Financial health · 2025

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.0%
Good
Equity as a share of total capital

Who owns HT BOLIG AS?

HT BOLIG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HT BOLIG AS

Who owns HT BOLIG AS?

JONDIG INVEST AS is the largest registered owner, with 50.0%.

Where is HT BOLIG AS based?

HT BOLIG AS has its business address in Øvrebø.

Property

Business address c/o Jondig Invest AS Holtanvegen 5, 4715 Øvrebø
Cadastral unit 4223-29/55/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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