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

NORDPÅ TAKST AS

Org. no. 923814302 Limited company (AS) Vestvågøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 190,000
Operating profit NOK 6,000
Equity NOK −19,000
Incorporated 2019
Share capital NOK 60,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−19k kr).

NORDPÅ TAKST AS is registered as a limited company in Vestvågøy, Nordland with organisation number 923814302. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 150 shares. The company's stated purpose is: “Taksering og salg av tjenester, samt utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 190,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 190,000
Operating profit
NOK 6,000
Equity
NOK −19,000
Est. value
NOK 65,000

Financial health · 2025

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-63.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NORDPÅ TAKST AS?

TAKSTMO AS
NORDPÅ TAKST AS
NOK 190,000 rev. · NOK 6,000 profit

NORDPÅ TAKST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORDPÅ TAKST AS

Who owns NORDPÅ TAKST AS?

TAKSTMO AS is the largest registered owner, with 33.3%.

What is the revenue of NORDPÅ TAKST AS?

NORDPÅ TAKST AS had revenue of NOK 190,000 in 2025.

Who is the general manager of NORDPÅ TAKST AS?

Kristian Flaaten Olsen is registered as general manager of NORDPÅ TAKST AS.

Where is NORDPÅ TAKST AS based?

NORDPÅ TAKST AS has its business address in Leknes.

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.