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

SLETTO TAKST AS

Org. no. 920225241 Limited company (AS) Ål Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 793,000
Equity NOK 2.4m
Incorporated 2018
Share capital NOK 30,000

SLETTO TAKST AS is registered as a limited company in Ål, Buskerud with organisation number 920225241. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Taksering og byggeteknisk konsulentvirksomhet og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 793,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 793,000
Equity
NOK 2.4m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns SLETTO TAKST AS?

GEIR SLETTO
SLETTO TAKST AS
NOK 3.0m rev. · NOK 793,000 profit

SLETTO TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLETTO TAKST AS

Who owns SLETTO TAKST AS?

GEIR SLETTO is the largest registered owner, with 100.0%.

What is the revenue of SLETTO TAKST AS?

SLETTO TAKST AS had revenue of NOK 3.0m in 2025.

Who is the general manager of SLETTO TAKST AS?

Geir Sletto is registered as general manager of SLETTO TAKST AS.

Where is SLETTO TAKST AS based?

SLETTO TAKST AS has its business address in Ål.

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.