BIZTRAC BETA
Uoppgitt

FINSRUD INVEST AS

Org. no. 832829102 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 13,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

FINSRUD INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 832829102. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investeringer. Dette inkluderer, men er ikke begrenset til, å investere i aksjer, obligasjoner, eiendom, verdipapirer og andre finansielle instrumenter. Videre kan selskapet delta i andre former for økonomiske aktiviteter som er relatert, men ikke begrenset til investeringer.”. 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 13,000
Est. value
NOK 15,000

Financial health · 2025

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

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

Who owns FINSRUD INVEST AS?

KRISTIAN FINSRUD
FINSRUD INVEST AS
NOK 0 rev. · NOK −6,000 profit

FINSRUD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FINSRUD INVEST AS

Who owns FINSRUD INVEST AS?

KRISTIAN FINSRUD is the largest registered owner, with 100.0%.

What is the revenue of FINSRUD INVEST AS?

FINSRUD INVEST AS had revenue of NOK 0 in 2025.

Where is FINSRUD INVEST AS based?

FINSRUD INVEST AS has its business address in Trondheim.

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.