BIZTRAC BETA
Rental and operating of own or leased real estate

HITT INVEST AS

Org. no. 934463544 Limited company (AS) Harstad Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 14,000
Operating profit NOK 5,000
Equity NOK 3,000
Incorporated 2024
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.

HITT INVEST AS is registered as a limited company in Harstad, Troms with organisation number 934463544. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom samt andre tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 14,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2024

Revenue
NOK 14,000
Operating profit
NOK 5,000
Equity
NOK 3,000
Est. value
NOK 10,000

Financial health · 2024

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.1%
Weak
Equity as a share of total capital

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

Who owns HITT INVEST AS?

TKM HOLDING AS
HITT INVEST AS
NOK 14,000 rev. · NOK 5,000 profit

HITT INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HITT INVEST AS

Who owns HITT INVEST AS?

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

What is the revenue of HITT INVEST AS?

HITT INVEST AS had revenue of NOK 14,000 in 2024.

Where is HITT INVEST AS based?

HITT INVEST AS has its business address in Harstad.

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.