BIZTRAC BETA
Rental and operating of own or leased real estate

ROM SAGBRUK AS

Org. no. 997467116 Limited company (AS) Lyngdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 3.4m
Equity NOK 6.0m
Incorporated 2011
Share capital NOK 112,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ROM SAGBRUK AS is registered as a limited company in Lyngdal, Agder with organisation number 997467116. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 112,000, divided into 1116 shares. The company's stated purpose is: “Å eie eiendommen Fiboveien 2A og 2B, gnr. 156, bnr. 172 og 173 i Lyngdal kommune, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 3.4m in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 3.4m
Equity
NOK 6.0m
Est. value
NOK 9.0m

Financial health · 2024

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.9%
Satisfactory
Equity as a share of total capital

Who owns ROM SAGBRUK AS?

SØRVEST KONTOREIENDOM AS
ROM SAGBRUK AS
NOK 7.1m rev. · NOK 3.4m profit

ROM SAGBRUK AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ROM SAGBRUK AS er morselskap for 1 datterselskap:

Frequently asked questions about ROM SAGBRUK AS

Who owns ROM SAGBRUK AS?

SØRVEST KONTOREIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ROM SAGBRUK AS?

ROM SAGBRUK AS had revenue of NOK 7.1m in 2024.

Where is ROM SAGBRUK AS based?

ROM SAGBRUK AS has its business address in Lyngdal.

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.