BIZTRAC BETA
Construction of residential and non-residential buildings

INGELSRUDØYA AS

Org. no. 936379516 Limited company (AS) Eidskog Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 202,000
Operating profit NOK 6,000
Equity NOK 35,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-06.

INGELSRUDØYA AS is registered as a limited company in Eidskog, Innlandet with organisation number 936379516. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tømrertjenester, inkludert, men ikke begrenset til, oppføring, vedlikehold, og reparasjon av bygninger, konstruksjon av trestrukturer, og andre relaterte tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 202,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 202,000
Operating profit
NOK 6,000
Equity
NOK 35,000
Est. value
NOK 32,000

Financial health · 2025

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

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

Who owns INGELSRUDØYA AS?

KIM INGELSRUDØYA
INGELSRUDØYA AS
NOK 202,000 rev. · NOK 6,000 profit

INGELSRUDØYA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INGELSRUDØYA AS

Who owns INGELSRUDØYA AS?

KIM INGELSRUDØYA is the largest registered owner, with 100.0%.

What is the revenue of INGELSRUDØYA AS?

INGELSRUDØYA AS had revenue of NOK 202,000 in 2025.

Where is INGELSRUDØYA AS based?

INGELSRUDØYA AS has its business address in Vestmarka.

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.