biztrac. BETA
COMPANY REGISTER PROFILE
930475181 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

TØMRER FUGELSØY AS

Org. no. 930475181 Limited company (AS) Surnadal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 8.3m
Operating profit NOK 334,000
Equity NOK 243,000
Incorporated 2022
Employees 6
Share capital NOK 30,000

TØMRER FUGELSØY AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 930475181. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømrerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.3m in revenue and NOK 334,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.3m
▲ +20 %
Operating profit
NOK 334,000
▲ +165 %
Equity
NOK 243,000
▲ +199 %
Est. value
NOK 890,000

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
17.5%
Very good
Return on total assets
Solidity
13.2%
Satisfactory
Equity as a share of total capital

Who owns TØMRER FUGELSØY AS?

TØMRER FUGELSØY AS
NOK 8.3m rev. · NOK 334,000 profit

TØMRER FUGELSØY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØMRER FUGELSØY AS

Who owns TØMRER FUGELSØY AS?

Kjetil Fugelsøy is the largest registered owner, with 100.0%.

What is the revenue of TØMRER FUGELSØY AS?

TØMRER FUGELSØY AS had revenue of NOK 8.3m in 2025.

Who is the general manager of TØMRER FUGELSØY AS?

Ingvild Bye Fugelsøy is registered as general manager of TØMRER FUGELSØY AS.

Where is TØMRER FUGELSØY AS based?

TØMRER FUGELSØY AS has its business address in Øvre Surnadal.

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.