BIZTRAC BETA
Office administrative and support activities

BRYN SERVICE AS

Org. no. 920387977 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 52,000
Operating profit NOK 46,000
Equity NOK −91,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−91k kr).

BRYN SERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 920387977. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kontortjenester og det som naturlig følger.”. The most recent filed accounts, for the 2025 financial year, show NOK 52,000 in revenue and NOK 46,000 in operating profit.

Key figures · 2025

Revenue
NOK 52,000
Operating profit
NOK 46,000
Equity
NOK −91,000
Est. value
NOK 219,000

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-133.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BRYN SERVICE AS?

WILLY ROGER AMUNDSEN
BRYN SERVICE AS
NOK 52,000 rev. · NOK 46,000 profit

BRYN SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRYN SERVICE AS

Who owns BRYN SERVICE AS?

WILLY ROGER AMUNDSEN is the largest registered owner, with 100.0%.

What is the revenue of BRYN SERVICE AS?

BRYN SERVICE AS had revenue of NOK 52,000 in 2025.

Who is the general manager of BRYN SERVICE AS?

Willy Roger Amundsen is registered as general manager of BRYN SERVICE AS.

Where is BRYN SERVICE AS based?

BRYN SERVICE AS has its business address in Oslo.

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.