BIZTRAC BETA
Uoppgitt

MIDTSKOG INVEST AS

Org. no. 936746047 Limited company (AS) Nord-Fron Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-12-09.

MIDTSKOG INVEST AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 936746047. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

Liquidity
4.62
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
78.3%
Weak
Equity as a share of total capital

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

Who owns MIDTSKOG INVEST AS?

TJØSTOLV MIDTSKOG
MIDTSKOG INVEST AS
NOK 0 rev. · NOK 0 profit

MIDTSKOG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDTSKOG INVEST AS

Who owns MIDTSKOG INVEST AS?

TJØSTOLV MIDTSKOG is the largest registered owner, with 100.0%.

What is the revenue of MIDTSKOG INVEST AS?

MIDTSKOG INVEST AS had revenue of NOK 0.

Who is the general manager of MIDTSKOG INVEST AS?

Tjøstolv Midtskog is registered as general manager of MIDTSKOG INVEST AS.

Where is MIDTSKOG INVEST AS based?

MIDTSKOG INVEST AS has its business address in Vinstra.

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.