BIZTRAC BETA
COMPANY REGISTER PROFILE
814508072 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Retail sale of articles for lighting

RYGG BELYSNING AS

Org. no. 814508072 Limited company (AS) Randaberg Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK −899,000
Equity NOK 300,000
Incorporated 2014
Share capital NOK 300,000

Signals

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

RYGG BELYSNING AS is registered as a limited company in Randaberg, Rogaland with organisation number 814508072. The business is classified under retail sale of articles for lighting (NACE 47.552). The company was incorporated in 2014. Registered share capital is NOK 300,000, divided into 1000 shares. The company's stated purpose is: “Drive med handel, herunder salg av belysning og hva som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK −899,000 in operating profit.

Former names: NYE RYGG BELYSNING AS

Key figures · 2025

Revenue
NOK 1.7m
▼ −52 %
Operating profit
NOK −899,000
▲ +29 %
Equity
NOK 300,000
▼ −69 %
Est. value
NOK 710,000

Financial health · 2025

Liquidity
1.16
Satisfactory
Current assets ÷ current liabilities
Profitability
-42.2%
Not satisfactory
Return on total assets
Solidity
13.8%
Satisfactory
Equity as a share of total capital

Who owns RYGG BELYSNING AS?

RYGG BELYSNING AS
NOK 1.7m rev. · NOK −899,000 profit

RYGG BELYSNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RYGG BELYSNING AS

Who owns RYGG BELYSNING AS?

HARESTAD ELEKTRISKE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RYGG BELYSNING AS?

RYGG BELYSNING AS had revenue of NOK 1.7m in 2025.

Where is RYGG BELYSNING AS based?

RYGG BELYSNING AS has its business address in Randaberg.

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

Report a problem

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