biztrac. BETA
COMPANY REGISTER PROFILE
917309906 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
All other professional, scientific and technical activities n.e.c.

FRØYEN TAKST AS

Org. no. 917309906 Limited company (AS) Solund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 88,000
Equity NOK 577,000
Incorporated 2016
Share capital NOK 30,000

FRØYEN TAKST AS is registered as a limited company in Solund, Vestland with organisation number 917309906. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Taksering og byggmestervirksomhet innen byggebransjen og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 88,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
▼ −15 %
Operating profit
NOK 88,000
▼ −70 %
Equity
NOK 577,000
▼ −29 %
Est. value
NOK 977,000

Financial health · 2024

Liquidity
-2.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
13.4%
Good
Return on total assets
Solidity
185.9%
Very good
Equity as a share of total capital

Who owns FRØYEN TAKST AS?

FRØYEN TAKST AS
NOK 3.0m rev. · NOK 88,000 profit

FRØYEN TAKST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRØYEN TAKST AS

Who owns FRØYEN TAKST AS?

Thomas Frøyen is the largest registered owner, with 50.0%.

What is the revenue of FRØYEN TAKST AS?

FRØYEN TAKST AS had revenue of NOK 3.0m in 2024.

Who is the general manager of FRØYEN TAKST AS?

Thomas Frøyen is registered as general manager of FRØYEN TAKST AS.

Where is FRØYEN TAKST AS based?

FRØYEN TAKST AS has its business address in Hardbakke.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.