BIZTRAC BETA
Rental and operating of own or leased real estate

GEISCHA AS

Org. no. 989175610 Limited company (AS) Lillehammer Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −73,000
Equity NOK 22.5m
Incorporated 2005
Share capital NOK 330,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−73k kr).

GEISCHA AS is registered as a limited company in Lillehammer, Innlandet with organisation number 989175610. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 330,000, divided into 1100 shares. The company's stated purpose is: “Investering og deltakelse i andre virksomheter samt investering i fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −73,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −73,000
Equity
NOK 22.5m
Est. value
NOK 22.1m

Financial health · 2024

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

Who owns GEISCHA AS?

ERIK MARTINIUS OTTESEN
GEISCHA AS
NOK 0 rev. · NOK −73,000 profit

GEISCHA AS has 4 registered shareholders:

All shareholders and roles →

Which companies does GEISCHA AS own?

GEISCHA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GEISCHA AS

Who owns GEISCHA AS?

ERIK MARTINIUS OTTESEN is the largest registered owner, with 59.1%.

What is the revenue of GEISCHA AS?

GEISCHA AS had revenue of NOK 0 in 2025.

Who is the general manager of GEISCHA AS?

Erik Martinius Ottesen is registered as general manager of GEISCHA AS.

Where is GEISCHA AS based?

GEISCHA AS has its business address in Lillehammer.

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.