biztrac. BETA
COMPANY REGISTER PROFILE
912346021 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠Y. KROGSTAD INVEST AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

Y. KROGSTAD INVEST AS

Org. no. 912346021 Limited company (AS) Vågan Incorporated 2013 In liquidation
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK −139,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−139k kr).

Y. KROGSTAD INVEST AS is registered as a limited company in Vågan, Nordland with organisation number 912346021. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i aksjer, eiendom og finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
▼ −0 %
Equity
NOK −139,000
▼ −1 %

Financial health · 2025

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

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

Who owns Y. KROGSTAD INVEST AS?

Y. KROGSTAD INVEST AS
NOK 0 rev. · NOK −2,000 profit

Y. KROGSTAD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Y. KROGSTAD INVEST AS

Who owns Y. KROGSTAD INVEST AS?

Yngve Krogstad is the largest registered owner, with 100.0%.

What is the revenue of Y. KROGSTAD INVEST AS?

Y. KROGSTAD INVEST AS had revenue of NOK 0 in 2025.

Where is Y. KROGSTAD INVEST AS based?

Y. KROGSTAD INVEST AS has its business address in Svolvær.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.