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

FJELLBUENE AS

Org. no. 919368322 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 350,000
Operating profit NOK 118,000
Equity NOK 4.0m
Incorporated 2017
Share capital NOK 6.0m

FJELLBUENE AS is registered as a limited company in Bærum, Akershus with organisation number 919368322. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 6.0m, divided into 2010000 shares. The company's stated purpose is: “Kjøp, drift, utleie og salg av fast eiendom og det som står i forbindelse med dette, herunder å delta i andre selskaper med slikt formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 350,000 in revenue and NOK 118,000 in operating profit.

Key figures · 2025

Revenue
NOK 350,000
▲ +41 %
Operating profit
NOK 118,000
▲ +2776 %
Equity
NOK 4.0m
▲ +1 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.3%
Weak
Return on total assets
Solidity
74.2%
Very good
Equity as a share of total capital

Who owns FJELLBUENE AS?

FJELLBUENE AS
NOK 350,000 rev. · NOK 118,000 profit

FJELLBUENE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJELLBUENE AS

Who owns FJELLBUENE AS?

Inger Kristine Reinås is the largest registered owner, with 100.0%.

What is the revenue of FJELLBUENE AS?

FJELLBUENE AS had revenue of NOK 350,000 in 2025.

Who is the general manager of FJELLBUENE AS?

Lars Christian Aasen is registered as general manager of FJELLBUENE AS.

Where is FJELLBUENE AS based?

FJELLBUENE AS has its business address in Lysaker.

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.