BIZTRAC BETA
Computer programming activities

SETTLE IN EUROPE AS

Org. no. 985547343 Limited company (AS) Eidskog Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 32,000
Operating profit NOK 10,000
Equity NOK −201,000
Incorporated 2003
Share capital NOK 100,000

Signals

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

SETTLE IN EUROPE AS is registered as a limited company in Eidskog, Innlandet with organisation number 985547343. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utvikling av kvalitetssikringssystemer, internettløsninger samt undervisning knyttet opp mot eiendomsmarkedet, herunder ved eierskap i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 32,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2024

Revenue
NOK 32,000
Operating profit
NOK 10,000
Equity
NOK −201,000
Est. value
NOK 72,000

Financial health · 2024

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

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

Who owns SETTLE IN EUROPE AS?

KJELL TERJE REPSHUS
SETTLE IN EUROPE AS
NOK 32,000 rev. · NOK 10,000 profit

SETTLE IN EUROPE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SETTLE IN EUROPE AS

Who owns SETTLE IN EUROPE AS?

KJELL TERJE REPSHUS is the largest registered owner, with 100.0%.

What is the revenue of SETTLE IN EUROPE AS?

SETTLE IN EUROPE AS had revenue of NOK 32,000 in 2024.

Where is SETTLE IN EUROPE AS based?

SETTLE IN EUROPE AS has its business address in Skotterud.

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.