BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

AMAFINE TAKST AS

Org. no. 914889162 Limited company (AS) Sandefjord Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 126,000
Operating profit NOK 49,000
Equity NOK 917
Incorporated 2015
Share capital NOK 30,000

AMAFINE TAKST AS is registered as a limited company in Sandefjord, Vestfold with organisation number 914889162. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Takseringsvirksomhet, prosjektledelse, byggevirksomhet og eiendomsdrift og det som hører med under disse områdene.”. The most recent filed accounts, for the 2025 financial year, show NOK 126,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 126,000
Operating profit
NOK 49,000
Equity
NOK 917
Est. value
NOK 152,000

Financial health · 2025

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

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

Who owns AMAFINE TAKST AS?

PER-OVE BØRUFSEN
AMAFINE TAKST AS
NOK 126,000 rev. · NOK 49,000 profit

AMAFINE TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMAFINE TAKST AS

Who owns AMAFINE TAKST AS?

PER-OVE BØRUFSEN is the largest registered owner, with 100.0%.

What is the revenue of AMAFINE TAKST AS?

AMAFINE TAKST AS had revenue of NOK 126,000 in 2025.

Who is the general manager of AMAFINE TAKST AS?

Per-Ove Børufsen is registered as general manager of AMAFINE TAKST AS.

Where is AMAFINE TAKST AS based?

AMAFINE TAKST AS has its business address in Sandefjord.

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.