BIZTRAC BETA
Construction of residential and non-residential buildings

NESTTUN TAKSERING AS

Org. no. 989867083 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 53,000
Equity NOK 172,000
Incorporated 2006
Share capital NOK 100,000

NESTTUN TAKSERING AS is registered as a limited company in Bergen, Vestland with organisation number 989867083. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Nybygg, rehabilitering, vedlikehold, verdi og lånetaksering, skade og branntaksering, boligsalgsrapporter, samt investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 53,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 53,000
Equity
NOK 172,000
Est. value
NOK 263,000

Financial health · 2025

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

Who owns NESTTUN TAKSERING AS?

ROGER JOHANNESSEN
NESTTUN TAKSERING AS
NOK 1.7m rev. · NOK 53,000 profit

NESTTUN TAKSERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESTTUN TAKSERING AS

Who owns NESTTUN TAKSERING AS?

ROGER JOHANNESSEN is the largest registered owner, with 100.0%.

What is the revenue of NESTTUN TAKSERING AS?

NESTTUN TAKSERING AS had revenue of NOK 1.7m in 2025.

Who is the general manager of NESTTUN TAKSERING AS?

Roger Johannessen is registered as general manager of NESTTUN TAKSERING AS.

Where is NESTTUN TAKSERING AS based?

NESTTUN TAKSERING AS has its business address in Nesttun.

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.