BIZTRAC BETA
Architectural activities

ROMLY AS

Org. no. 920528791 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK −116,000
Equity NOK 128,000
Incorporated 2018
Share capital NOK 31,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−116k kr).

ROMLY AS is registered as a limited company in Oslo, Oslo with organisation number 920528791. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2018. Registered share capital is NOK 31,000, divided into 31435 shares. The company's stated purpose is: “3D-laserskanning, produksjon, vedlikehold og distribusjon av digitale tvillinger og tilhørende data av eiendom samt tilliggende tjenester og utvikling av programvare. Herunder investering i andre selskaper, samt annen virksomhet som naturlig faller inn under denne forretningsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK −116,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK −116,000
Equity
NOK 128,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.5%
Weak
Equity as a share of total capital

Who owns ROMLY AS?

FUTUREPROOF AS
ROMLY AS
NOK 1.3m rev. · NOK −116,000 profit

ROMLY AS has 5 registered shareholders:

All shareholders and roles →

Which companies does ROMLY AS own?

ROMLY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ROMLY AS

Who owns ROMLY AS?

FUTUREPROOF AS is the largest registered owner, with 70.4%.

What is the revenue of ROMLY AS?

ROMLY AS had revenue of NOK 1.3m in 2024.

Where is ROMLY AS based?

ROMLY AS has its business address in Oslo.

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.