BIZTRAC BETA
Business and other management consultancy activities

FIGENSCHAU HOLDING AS

Org. no. 918644245 Limited company (AS) Tromsø Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 568,000
Equity NOK 407,000
Incorporated 2016
Share capital NOK 30,000

FIGENSCHAU HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 918644245. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, finansielle tjenester og medvirke i andre selskaper innen for nærliggende virksomhet, samt annet som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 568,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 568,000
Equity
NOK 407,000
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns FIGENSCHAU HOLDING AS?

KURT FIGENSCHAU
FIGENSCHAU HOLDING AS
NOK 2.8m rev. · NOK 568,000 profit

FIGENSCHAU HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FIGENSCHAU HOLDING AS

Who owns FIGENSCHAU HOLDING AS?

KURT FIGENSCHAU is the largest registered owner, with 100.0%.

What is the revenue of FIGENSCHAU HOLDING AS?

FIGENSCHAU HOLDING AS had revenue of NOK 2.8m in 2024.

Who is the general manager of FIGENSCHAU HOLDING AS?

Kurt Figenschau is registered as general manager of FIGENSCHAU HOLDING AS.

Where is FIGENSCHAU HOLDING AS based?

FIGENSCHAU HOLDING AS has its business address in Tromsø.

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.