BIZTRAC BETA
Construction of residential and non-residential buildings

FJORDANE BYGG AS

Org. no. 927680513 Limited company (AS) Stryn Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 899,000
Operating profit NOK 41,000
Equity NOK 77,000
Incorporated 2021
Share capital NOK 30,000

FJORDANE BYGG AS is registered as a limited company in Stryn, Vestland with organisation number 927680513. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bygg- og anleggsvirksomhet, og alt som herved står i forbindelse, herunder ved oppkjøp av aksjar m.v. å kunne gjere seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 899,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2024

Revenue
NOK 899,000
Operating profit
NOK 41,000
Equity
NOK 77,000
Est. value
NOK 185,000

Financial health · 2024

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

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

Who owns FJORDANE BYGG AS?

FREDRIK SKREDE
FJORDANE BYGG AS
NOK 899,000 rev. · NOK 41,000 profit

FJORDANE BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJORDANE BYGG AS

Who owns FJORDANE BYGG AS?

FREDRIK SKREDE is the largest registered owner, with 50.0%.

What is the revenue of FJORDANE BYGG AS?

FJORDANE BYGG AS had revenue of NOK 899,000 in 2024.

Who is the general manager of FJORDANE BYGG AS?

Rikard Blindheim is registered as general manager of FJORDANE BYGG AS.

Where is FJORDANE BYGG AS based?

FJORDANE BYGG AS has its business address in Utvik.

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.