biztrac. BETA
COMPANY REGISTER PROFILE
912289729 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

FLØYBYEN AS

Org. no. 912289729 Limited company (AS) Arendal Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 904,000
Equity NOK 52.7m
Incorporated 2013
Share capital NOK 1.5m

FLØYBYEN AS is registered as a limited company in Arendal, Agder with organisation number 912289729. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 1.5m, divided into 759 shares. The company's stated purpose is: “Eiendomsutvikling, herunder kjøp, salg og utleie av fast eiendom samt hva som hører naturlig sammen med dette. Selskapet kan også eie andeler i øvrige selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 904,000 in operating profit.

Former names: SJØMANNSSKOLEN AS

Key figures · 2025

Revenue
NOK 1.6m
▲ +4 %
Operating profit
NOK 904,000
▲ +35 %
Equity
NOK 52.7m
▲ +1 %
Est. value
NOK 37.4m

Financial health · 2025

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
1.5%
Weak
Return on total assets
Solidity
75.1%
Very good
Equity as a share of total capital

Who owns FLØYBYEN AS?

FLØYBYEN AS
NOK 1.6m rev. · NOK 904,000 profit

FLØYBYEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLØYBYEN AS

Who owns FLØYBYEN AS?

ARENDAL NÆRINGSSELSKAP AS is the largest registered owner, with 100.0%.

What is the revenue of FLØYBYEN AS?

FLØYBYEN AS had revenue of NOK 1.6m in 2025.

Who is the general manager of FLØYBYEN AS?

Per Johnsen is registered as general manager of FLØYBYEN AS.

Where is FLØYBYEN AS based?

FLØYBYEN AS has its business address in Arendal.

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.