biztrac. BETA
COMPANY REGISTER PROFILE
998593794 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

GISLEVOLD SKOG NORD ANS

Org. no. 998593794 General partnership (ANS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 284,000
Operating profit NOK −1,000
Equity NOK 518,000
Incorporated 2012

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).
  • Nylig endring 2026-10-06 Adresseendring registrert 2026-10-06.

GISLEVOLD SKOG NORD ANS is registered as a general partnership in Oslo, Oslo with organisation number 998593794. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2012. The company's stated purpose is: “Eie og forvalte fast eiendom. ”. The most recent filed accounts, for the 2025 financial year, show NOK 284,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 284,000
▼ −82 %
Operating profit
NOK −1,000
▼ −100 %
Equity
NOK 518,000
▲ +13 %
Est. value
NOK 738,000

Financial health · 2025

Liquidity
24.14
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
96.8%
Very good
Equity as a share of total capital

Who owns GISLEVOLD SKOG NORD ANS?

No shareholders are registered for GISLEVOLD SKOG NORD ANS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GISLEVOLD SKOG NORD ANS

What is the revenue of GISLEVOLD SKOG NORD ANS?

GISLEVOLD SKOG NORD ANS had revenue of NOK 284,000 in 2025.

Who is the general manager of GISLEVOLD SKOG NORD ANS?

Christian Skattum is registered as general manager of GISLEVOLD SKOG NORD ANS.

Where is GISLEVOLD SKOG NORD ANS based?

GISLEVOLD SKOG NORD ANS has its business address in Oslo.

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.