BIZTRAC BETA
Rental and operating of own or leased real estate

SMIBYGG AS

Org. no. 831567392 Limited company (AS) Trondheim Incorporated 1977 Active
Ownership graph ↗
Revenue 2024 NOK 26.2m
Operating profit NOK 18.3m
Equity NOK 31.5m
Incorporated 1977
Share capital NOK 8.1m

Signals

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

SMIBYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 831567392. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1977. Registered share capital is NOK 8.1m, divided into 109000 shares. The company's stated purpose is: “Å eie, drifte, vedllikeholde og utvikle fast eiendom og hermed beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.2m in revenue and NOK 18.3m in operating profit.

Key figures · 2024

Revenue
NOK 26.2m
Operating profit
NOK 18.3m
Equity
NOK 31.5m
Est. value
NOK 53.7m

Financial health · 2024

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

Who owns SMIBYGG AS?

E.A. SMITH AS
SMIBYGG AS
NOK 26.2m rev. · NOK 18.3m profit

SMIBYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SMIBYGG AS er morselskap for 7 datterselskaper:

Frequently asked questions about SMIBYGG AS

Who owns SMIBYGG AS?

E.A. SMITH AS is the largest registered owner, with 100.0%.

What is the revenue of SMIBYGG AS?

SMIBYGG AS had revenue of NOK 26.2m in 2024.

Who is the general manager of SMIBYGG AS?

Arne Reinertsen is registered as general manager of SMIBYGG AS.

Where is SMIBYGG AS based?

SMIBYGG AS has its business address in Heimdal.

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.