BIZTRAC BETA
Construction of residential and non-residential buildings

REMDA BYGG AS

Org. no. 928723879 Limited company (AS) Ås Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 11,000
Equity NOK 516,000
Incorporated 2021
Employees 6
Share capital NOK 30,000

REMDA BYGG AS is registered as a limited company in Ås, Akershus with organisation number 928723879. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utføre snekker-, blikkenslager-, betong-, og anleggsarbeider, konsulenttjenester innenfor bygg og anlegg, samt alt hva hermed står i forbindelse. Kjøp og salg av byggematerialer samt produkter knyttet til byggebransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 11,000
Equity
NOK 516,000
Est. value
NOK 264,000

Financial health · 2025

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.5%
Good
Equity as a share of total capital

Who owns REMDA BYGG AS?

DARIUS MESKAUSKAS
REMDA BYGG AS
NOK 3.6m rev. · NOK 11,000 profit

REMDA BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REMDA BYGG AS

Who owns REMDA BYGG AS?

DARIUS MESKAUSKAS is the largest registered owner, with 50.0%.

What is the revenue of REMDA BYGG AS?

REMDA BYGG AS had revenue of NOK 3.6m in 2025.

Who is the general manager of REMDA BYGG AS?

Remigijus Zareckij is registered as general manager of REMDA BYGG AS.

Where is REMDA BYGG AS based?

REMDA BYGG AS has its business address in Vinterbro.

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.