BIZTRAC BETA
Buying and selling of own real estate

IN LOCO AS

Org. no. 988735671 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −30,000
Equity NOK 1.3m
Incorporated 2005
Share capital NOK 102,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−30k kr).

IN LOCO AS is registered as a limited company in Kristiansand, Agder with organisation number 988735671. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 102,000, divided into 101695 shares. The company's stated purpose is: “Anskaffelse og drift av eiendommer, investeringer i andre selskaper, handel samt alt hva dermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK 1.3m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns IN LOCO AS?

NERE GUNSTEINSON SKOMEDAL
IN LOCO AS
NOK 0 rev. · NOK −30,000 profit

IN LOCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IN LOCO AS own?

IN LOCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about IN LOCO AS

Who owns IN LOCO AS?

NERE GUNSTEINSON SKOMEDAL is the largest registered owner, with 100.0%.

What is the revenue of IN LOCO AS?

IN LOCO AS had revenue of NOK 0 in 2024.

Where is IN LOCO AS based?

IN LOCO AS has its business address in Søgne.

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.