BIZTRAC BETA
Business and other management consultancy activities

FINANSSENTERET NORDSTRAND AS

Org. no. 885415172 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 2005
Share capital NOK 100,000

FINANSSENTERET NORDSTRAND AS is registered as a limited company in Oslo, Oslo with organisation number 885415172. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Finansiellrådgivning innen bank, fond og forsikring. Deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2024

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

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

Who owns FINANSSENTERET NORDSTRAND AS?

KNUT HAUGANE
FINANSSENTERET NORDSTRAND AS
NOK 0 rev. · NOK 0 profit

FINANSSENTERET NORDSTRAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FINANSSENTERET NORDSTRAND AS

Who owns FINANSSENTERET NORDSTRAND AS?

KNUT HAUGANE is the largest registered owner, with 100.0%.

What is the revenue of FINANSSENTERET NORDSTRAND AS?

FINANSSENTERET NORDSTRAND AS had revenue of NOK 0 in 2024.

Who is the general manager of FINANSSENTERET NORDSTRAND AS?

Knut Haugane is registered as general manager of FINANSSENTERET NORDSTRAND AS.

Where is FINANSSENTERET NORDSTRAND AS based?

FINANSSENTERET NORDSTRAND AS has its business address in Oslo.

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.