BIZTRAC BETA
Uoppgitt

T. INDRESAND INVEST AS

Org. no. 932305046 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 16,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

T. INDRESAND INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 932305046. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Deltakelse i annen virksomhet. Investering i aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 16,000
Est. value
NOK 19,000

Financial health · 2025

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

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

Who owns T. INDRESAND INVEST AS?

THEA HANSINE PERSON INDRESAND
T. INDRESAND INVEST AS
NOK 0 rev. · NOK −6,000 profit

T. INDRESAND INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does T. INDRESAND INVEST AS own?

T. INDRESAND INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about T. INDRESAND INVEST AS

Who owns T. INDRESAND INVEST AS?

THEA HANSINE PERSON INDRESAND is the largest registered owner, with 100.0%.

What is the revenue of T. INDRESAND INVEST AS?

T. INDRESAND INVEST AS had revenue of NOK 0 in 2025.

Where is T. INDRESAND INVEST AS based?

T. INDRESAND INVEST AS has its business address in Drammen.

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.