BIZTRAC BETA
Retail sale of medical and orthopaedic goods

SKYTTERBRILLER.NO AS

Org. no. 992037377 Limited company (AS) Arendal Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 35,000
Equity NOK 101,000
Incorporated 2007
Share capital NOK 100,000

SKYTTERBRILLER.NO AS is registered as a limited company in Arendal, Agder with organisation number 992037377. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Vareomsetning og tjenesteyting i forbindelse med omsetning av briller og andre relaterte produkter, ytelse av eie, omsetning og investering i aksjer i andre selskaper og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 35,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 35,000
Equity
NOK 101,000
Est. value
NOK 212,000

Financial health · 2025

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.6%
Weak
Equity as a share of total capital

Who owns SKYTTERBRILLER.NO AS?

AAGE BREKKE AS
SKYTTERBRILLER.NO AS
NOK 1.7m rev. · NOK 35,000 profit

SKYTTERBRILLER.NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKYTTERBRILLER.NO AS

Who owns SKYTTERBRILLER.NO AS?

AAGE BREKKE AS is the largest registered owner, with 100.0%.

What is the revenue of SKYTTERBRILLER.NO AS?

SKYTTERBRILLER.NO AS had revenue of NOK 1.7m in 2025.

Who is the general manager of SKYTTERBRILLER.NO AS?

Jan Brekke is registered as general manager of SKYTTERBRILLER.NO AS.

Where is SKYTTERBRILLER.NO AS based?

SKYTTERBRILLER.NO AS has its business address in Arendal.

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.