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

PERO TAKST AS

Org. no. 916643276 Limited company (AS) Lillehammer Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 380,000
Equity NOK 4.4m
Incorporated 2016
Share capital NOK 120,000

PERO TAKST AS is registered as a limited company in Lillehammer, Innlandet with organisation number 916643276. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2016. Registered share capital is NOK 120,000, divided into 1200 shares. The company's stated purpose is: “Taksering og rådgiving innen bygg og annet som står i forbindelse 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 1.0m in revenue and NOK 380,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 380,000
Equity
NOK 4.4m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns PERO TAKST AS?

PER OLAV RØNNING
PERO TAKST AS
NOK 1.0m rev. · NOK 380,000 profit

PERO TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PERO TAKST AS

Who owns PERO TAKST AS?

PER OLAV RØNNING is the largest registered owner, with 100.0%.

What is the revenue of PERO TAKST AS?

PERO TAKST AS had revenue of NOK 1.0m in 2025.

Who is the general manager of PERO TAKST AS?

Per Olav Rønning is registered as general manager of PERO TAKST AS.

Where is PERO TAKST AS based?

PERO TAKST 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.