BIZTRAC BETA
Construction of residential and non-residential buildings

SVEINE BYGG AS

Org. no. 936243363 Limited company (AS) Enebakk Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 670,000
Operating profit NOK 262,000
Equity NOK 230,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-09-02.

SVEINE BYGG AS is registered as a limited company in Enebakk, Akershus with organisation number 936243363. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tømrerarbeid og entreprenørvirksomhet, deltagelse i andre selskaper ved aksjetegning el. på annet vis.”. The most recent filed accounts, for the 2025 financial year, show NOK 670,000 in revenue and NOK 262,000 in operating profit.

Key figures · 2025

Revenue
NOK 670,000
Operating profit
NOK 262,000
Equity
NOK 230,000
Est. value
NOK 880,000

Financial health · 2025

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

Who owns SVEINE BYGG AS?

MAGNUS FJELLESTAD SVEINE
SVEINE BYGG AS
NOK 670,000 rev. · NOK 262,000 profit

SVEINE BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVEINE BYGG AS

Who owns SVEINE BYGG AS?

MAGNUS FJELLESTAD SVEINE is the largest registered owner, with 100.0%.

What is the revenue of SVEINE BYGG AS?

SVEINE BYGG AS had revenue of NOK 670,000 in 2025.

Who is the general manager of SVEINE BYGG AS?

Magnus Fjellestad Sveine is registered as general manager of SVEINE BYGG AS.

Where is SVEINE BYGG AS based?

SVEINE BYGG AS has its business address in Flateby.

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.