BIZTRAC BETA
Construction of residential and non-residential buildings

MORTERUD & RAMSE AS

Org. no. 964095353 Limited company (AS) Lillestrøm Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 678,000
Operating profit NOK −53,000
Equity NOK 837,000
Incorporated 1992
Share capital NOK 30,000

Signals

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

MORTERUD & RAMSE AS is registered as a limited company in Lillestrøm, Akershus with organisation number 964095353. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1992. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Grave- og entreprenørvirksomhet samt alt hva som står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 678,000 in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 678,000
Operating profit
NOK −53,000
Equity
NOK 837,000
Est. value
NOK 595,000

Financial health · 2025

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

Who owns MORTERUD & RAMSE AS?

KJELL RAMSE
MORTERUD & RAMSE AS
NOK 678,000 rev. · NOK −53,000 profit

MORTERUD & RAMSE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MORTERUD & RAMSE AS

Who owns MORTERUD & RAMSE AS?

KJELL RAMSE is the largest registered owner, with 50.0%.

What is the revenue of MORTERUD & RAMSE AS?

MORTERUD & RAMSE AS had revenue of NOK 678,000 in 2025.

Who is the general manager of MORTERUD & RAMSE AS?

Kjell Ramse is registered as general manager of MORTERUD & RAMSE AS.

Where is MORTERUD & RAMSE AS based?

MORTERUD & RAMSE AS has its business address in Fetsund.

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.