BIZTRAC BETA
Other technical consultancy

SIVILINGENIØR NILS RØMOEN AS

Org. no. 991868615 Limited company (AS) Lillehammer Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −332,000
Equity NOK 2.3m
Incorporated 2007
Share capital NOK 100,000

Signals

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

SIVILINGENIØR NILS RØMOEN AS is registered as a limited company in Lillehammer, Innlandet with organisation number 991868615. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og konsulenttjenester innen bygg og anlegg, produksjon av naturstein, investeringer, deltagelse i andre selskaper samt virksomhet forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −332,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −332,000
Equity
NOK 2.3m
Est. value
NOK 3.8m

Financial health · 2024

Liquidity
12.23
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
91.8%
Very good
Equity as a share of total capital

Who owns SIVILINGENIØR NILS RØMOEN AS?

NILS RØMOEN
SIVILINGENIØR NILS RØMOEN AS
NOK 0 rev. · NOK −332,000 profit

SIVILINGENIØR NILS RØMOEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIVILINGENIØR NILS RØMOEN AS

Who owns SIVILINGENIØR NILS RØMOEN AS?

NILS RØMOEN is the largest registered owner, with 100.0%.

What is the revenue of SIVILINGENIØR NILS RØMOEN AS?

SIVILINGENIØR NILS RØMOEN AS had revenue of NOK 0 in 2024.

Where is SIVILINGENIØR NILS RØMOEN AS based?

SIVILINGENIØR NILS RØMOEN AS has its business address in Lillehammer.

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.