BIZTRAC BETA
Construction of residential and non-residential buildings

FJETLAND TAKST AS

Org. no. 985834598 Limited company (AS) Haugesund Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 1.3m
Equity NOK 10.1m
Incorporated 2003
Share capital NOK 30,000

FJETLAND TAKST AS is registered as a limited company in Haugesund, Rogaland with organisation number 985834598. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2003. Registered share capital is NOK 30,000, divided into 4000 shares. The company's stated purpose is: “Handel, produksjon og tjenesteytelser i forbindelse med byggmestervirksomhet og takstering av fast eiendom samt hva hermed står i forbindelse, herunder å delta i enheter med samme virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 1.3m
Equity
NOK 10.1m
Est. value
NOK 8.7m

Financial health · 2025

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

Who owns FJETLAND TAKST AS?

JAN WILLY FJETLAND
FJETLAND TAKST AS
NOK 3.4m rev. · NOK 1.3m profit

FJETLAND TAKST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJETLAND TAKST AS

Who owns FJETLAND TAKST AS?

JAN WILLY FJETLAND is the largest registered owner, with 90.0%.

What is the revenue of FJETLAND TAKST AS?

FJETLAND TAKST AS had revenue of NOK 3.4m in 2025.

Who is the general manager of FJETLAND TAKST AS?

Jan Willy Fjetland is registered as general manager of FJETLAND TAKST AS.

Where is FJETLAND TAKST AS based?

FJETLAND TAKST AS has its business address in Haugesund.

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.