biztrac. BETA
COMPANY REGISTER PROFILE
833903772 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

RHINO BYGG AS

Org. no. 833903772 Limited company (AS) Giske Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 311,000
Equity NOK 257,000
Incorporated 2024
Share capital NOK 30,000

RHINO BYGG AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 833903772. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rehabilitering av bygg. Snekkerarbeid. Vaktmestertjenester. Generelle byggearbeider og andre lignende arbeider.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 311,000 in operating profit.

Former names: MM SERVICE BYGG AS

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 311,000
▲ +3606 %
Equity
NOK 257,000
▲ +1573 %
Est. value
NOK 941,000

Financial health · 2025

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
62.4%
Very good
Return on total assets
Solidity
26.4%
Good
Equity as a share of total capital

Who owns RHINO BYGG AS?

RHINO BYGG AS
NOK 3.2m rev. · NOK 311,000 profit

RHINO BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RHINO BYGG AS

Who owns RHINO BYGG AS?

Marcin Niec is the largest registered owner, with 100.0%.

What is the revenue of RHINO BYGG AS?

RHINO BYGG AS had revenue of NOK 3.2m in 2025.

Who is the general manager of RHINO BYGG AS?

Marcin Niec is registered as general manager of RHINO BYGG AS.

Where is RHINO BYGG AS based?

RHINO BYGG AS has its business address in Valderøya.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.