BIZTRAC BETA
Other captive investment companies

KRINGEN AS

Org. no. 918410813 Limited company (AS) Stjørdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 20,000
Operating profit NOK 294
Equity NOK −354,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

KRINGEN AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 918410813. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i og eie aksjer i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 20,000 in revenue and NOK 294 in operating profit.

Key figures · 2025

Revenue
NOK 20,000
Operating profit
NOK 294
Equity
NOK −354,000
Est. value
NOK 3,000

Financial health · 2025

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

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

Who owns KRINGEN AS?

TORE ANDRE KRINGEN
KRINGEN AS
NOK 20,000 rev. · NOK 294 profit

KRINGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRINGEN AS own?

KRINGEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KRINGEN AS

Who owns KRINGEN AS?

TORE ANDRE KRINGEN is the largest registered owner, with 100.0%.

What is the revenue of KRINGEN AS?

KRINGEN AS had revenue of NOK 20,000 in 2025.

Who is the general manager of KRINGEN AS?

Tore Andre Kringen is registered as general manager of KRINGEN AS.

Where is KRINGEN AS based?

KRINGEN AS has its business address in Stjørdal.

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.