BIZTRAC BETA
Business and other management consultancy activities

DIN BANKRÅDGIVER AS

Org. no. 998740436 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −62,000
Equity NOK −875,000
Incorporated 2012
Share capital NOK 502,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−875k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−62k kr).

DIN BANKRÅDGIVER AS is registered as a limited company in Bergen, Vestland with organisation number 998740436. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 502,000, divided into 200 shares. The company's stated purpose is: “Konsulenttjenester innenfor drift og utvikling av andre selskaper samt investere i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −62,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −62,000
Equity
NOK −875,000

Financial health · 2024

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

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

Who owns DIN BANKRÅDGIVER AS?

KARSTAD HOLDING AS
DIN BANKRÅDGIVER AS
NOK 0 rev. · NOK −62,000 profit

DIN BANKRÅDGIVER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIN BANKRÅDGIVER AS

Who owns DIN BANKRÅDGIVER AS?

KARSTAD HOLDING AS is the largest registered owner, with 51.0%.

What is the revenue of DIN BANKRÅDGIVER AS?

DIN BANKRÅDGIVER AS had revenue of NOK 0 in 2024.

Where is DIN BANKRÅDGIVER AS based?

DIN BANKRÅDGIVER AS has its business address in Paradis.

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.