BIZTRAC BETA
Uoppgitt

HILDBRANDSEN INVEST AS

Org. no. 929149688 Limited company (AS) Midtre Gauldal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 63,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

HILDBRANDSEN INVEST AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 929149688. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 63,000
Est. value
NOK 74,000

Financial health · 2025

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

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

Who owns HILDBRANDSEN INVEST AS?

JO MIKKEL SÆTER
HILDBRANDSEN INVEST AS
NOK 0 rev. · NOK −13,000 profit

HILDBRANDSEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HILDBRANDSEN INVEST AS own?

HILDBRANDSEN INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HILDBRANDSEN INVEST AS

Who owns HILDBRANDSEN INVEST AS?

JO MIKKEL SÆTER is the largest registered owner, with 100.0%.

What is the revenue of HILDBRANDSEN INVEST AS?

HILDBRANDSEN INVEST AS had revenue of NOK 0 in 2025.

Where is HILDBRANDSEN INVEST AS based?

HILDBRANDSEN INVEST AS has its business address in Soknedal.

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.