BIZTRAC BETA
Other real estate activities on a fee or contract basis

GEILO TAKST AS

Org. no. 988464848 Limited company (AS) Hol Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 234,000
Operating profit NOK −90,000
Equity NOK 550,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

GEILO TAKST AS is registered as a limited company in Hol, Buskerud with organisation number 988464848. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Taksering av eiendommer, prosjektoppfølging og ingeniørtjenester og alt som står i forbindelse med dette - herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 234,000 in revenue and NOK −90,000 in operating profit.

Key figures · 2025

Revenue
NOK 234,000
Operating profit
NOK −90,000
Equity
NOK 550,000
Est. value
NOK 728,000

Financial health · 2025

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

Who owns GEILO TAKST AS?

MAGNE SÆTHER
GEILO TAKST AS
NOK 234,000 rev. · NOK −90,000 profit

GEILO TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GEILO TAKST AS

Who owns GEILO TAKST AS?

MAGNE SÆTHER is the largest registered owner, with 100.0%.

What is the revenue of GEILO TAKST AS?

GEILO TAKST AS had revenue of NOK 234,000 in 2025.

Who is the general manager of GEILO TAKST AS?

Magne Sæther is registered as general manager of GEILO TAKST AS.

Where is GEILO TAKST AS based?

GEILO TAKST AS has its business address in Geilo.

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.