BIZTRAC BETA
Rental and operating of own or leased real estate

FRYDENBØLIEN AS

Org. no. 917686270 Limited company (AS) Bjørnafjorden Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 1.1m
Equity NOK 2.8m
Incorporated 2016
Share capital NOK 35,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FRYDENBØLIEN AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 917686270. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 35,000, divided into 35000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 1.1m
Equity
NOK 2.8m
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns FRYDENBØLIEN AS?

DRAGESET AS
FRYDENBØLIEN AS
NOK 1.4m rev. · NOK 1.1m profit

FRYDENBØLIEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRYDENBØLIEN AS

Who owns FRYDENBØLIEN AS?

DRAGESET AS is the largest registered owner, with 100.0%.

What is the revenue of FRYDENBØLIEN AS?

FRYDENBØLIEN AS had revenue of NOK 1.4m in 2025.

Who is the general manager of FRYDENBØLIEN AS?

Eva Solli Drageset is registered as general manager of FRYDENBØLIEN AS.

Where is FRYDENBØLIEN AS based?

FRYDENBØLIEN AS has its business address in Hagavik.

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.