biztrac. BETA
COMPANY REGISTER PROFILE
924295104 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

FJORDBYEN LIERSTRANDA UTVIKLING AS

Org. no. 924295104 Limited company (AS) Aurskog-Høland Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −280,000
Equity NOK 11.9m
Incorporated 2019
Share capital NOK 163,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−280k kr).

FJORDBYEN LIERSTRANDA UTVIKLING AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 924295104. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 163,000, divided into 162500 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.”.

Former names: ATHOMSTART INVEST 445 AS, BAKKE BOLIG FJORDBYEN AS

Key figures · 2025

Operating profit
NOK −280,000
▲ +2 %
Equity
NOK 11.9m
▼ −41 %
Est. value
NOK 10.8m

Financial health · 2025

Liquidity
24.86
Very good
Current assets ÷ current liabilities
Profitability
2.7%
Weak
Return on total assets
Solidity
5.1%
Weak
Equity as a share of total capital

Who owns FJORDBYEN LIERSTRANDA UTVIKLING AS?

FJORDBYEN LIERSTRANDA UTVIKLING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FJORDBYEN LIERSTRANDA UTVIKLING AS own?

FJORDBYEN LIERSTRANDA UTVIKLING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about FJORDBYEN LIERSTRANDA UTVIKLING AS

Who owns FJORDBYEN LIERSTRANDA UTVIKLING AS?

RESIDEV I AS is the largest registered owner, with 40.0%.

Where is FJORDBYEN LIERSTRANDA UTVIKLING AS based?

FJORDBYEN LIERSTRANDA UTVIKLING AS has its business address in Aurskog.

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.