BIZTRAC BETA
Development of building projects

FJERDINGBY SENTRUMSUTVIKLING AS

Org. no. 819766932 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 6.4m
Operating profit NOK 944,000
Equity NOK 1.6m
Incorporated 2017
Share capital NOK 380,000

FJERDINGBY SENTRUMSUTVIKLING AS is registered as a limited company in Asker, Akershus with organisation number 819766932. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 380,000, divided into 380 shares. The company's stated purpose is: “Eie, kjøp, utvikling og salg av fast eiendom samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.4m in revenue and NOK 944,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.4m
Operating profit
NOK 944,000
Equity
NOK 1.6m
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.1%
Good
Equity as a share of total capital

Who owns FJERDINGBY SENTRUMSUTVIKLING AS?

REBUS STOR-OSLO AS
FJERDINGBY SENTRUMSUTVIKLING AS
NOK 6.4m rev. · NOK 944,000 profit

FJERDINGBY SENTRUMSUTVIKLING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJERDINGBY SENTRUMSUTVIKLING AS

Who owns FJERDINGBY SENTRUMSUTVIKLING AS?

REBUS STOR-OSLO AS is the largest registered owner, with 35.0%.

What is the revenue of FJERDINGBY SENTRUMSUTVIKLING AS?

FJERDINGBY SENTRUMSUTVIKLING AS had revenue of NOK 6.4m in 2025.

Who is the general manager of FJERDINGBY SENTRUMSUTVIKLING AS?

Axel Bryde is registered as general manager of FJERDINGBY SENTRUMSUTVIKLING AS.

Where is FJERDINGBY SENTRUMSUTVIKLING AS based?

FJERDINGBY SENTRUMSUTVIKLING AS has its business address in Asker.

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.