トップ >
神奈川県でテニス!
このページのアクセス数
264
ウォッチリストに入れる
Tweet
金沢産業振興センターで楽しく中上級ダブルス
| 主催者 | lumber_hernia さん (男性) |
| 開催日時 |
2026-03-29(日) 15:00
から 2時間 |
|
参加申し込み 締め切り日時 |
2026-03-29(日) 13:05 |
| テニスコート | 1 面 種類: 全天候（オムニ） |
| 定員 | 3 人 （主催者本人及び主催者枠による参加者を除く） |
| 会場 | 金沢産業振興センター （神奈川県） |
| 会場の地図 | Googleマップによる地図と衛星写真 |
|
主催者への緊急連絡先(携帯等)：
設定されています。
主催者または承認済みの参加者がログインしている場合にのみ表示されます。
テニスオフ開催日の数日後以降は表示されなくなります。
|
|
iCalendarテニスオフ詳細情報
一般中上級程度の方を募集します。(主催者含めて4～5名を予定） 料金は 4名/面の場合￥1000/人, 5名/面の場合￥800/人 集合は直接コートにお越しください。 30分程度アップを行った後、４ゲーム消化（ノーアド）でペアを変えながら回して行きます。 雨天で中止の場合は開始時刻の1時間前までに追加情報を記載します
- 11/22 (日) 13:00 金沢産業振興センターで楽しく中上級ダブルス 締切
- 11/14 (土) 11:00 金沢産業振興センターで楽しく中上級ダブルス 参加者募集中
-
11/8 (日) 13:00
富岡西公園で楽しく中上級ダブルス
終了(オフレポ書き込み可)
オフレポ掲示板の投稿(2) - 11/3 (火) 13:00 金沢産業振興センターで楽しく中上級ダブルス 全て終了
- 11/1 (日) 13:00 金沢産業振興センターで楽しく中上級ダブルス 中止
-
10/31 (土) 13:00
金沢産業振興センターで楽しく中上級ダブルス
全て終了
オフレポ掲示板の投稿(1) - 10/25 (日) 15:00 金沢産業振興センターで楽しく中上級ダブルス 全て終了
-
10/18 (日) 15:00
金沢産業振興センターで楽しく中上級ダブルス
全て終了
オフレポ掲示板の投稿(2) - 10/12 (月) 15:00 金沢産業振興センターで楽しく中上級ダブルス 全て終了
- 10/10 (土) 15:00 金沢産業振興センターで楽しく中上級ダブルス 全て終了
-
主催者指定アラート
lumber_herniaさんが 新しいテニスオフを開催登録したときにメールでお知らせ -
都道府県アラート
神奈川県での 新しいテニスオフが登録されたときにメールでお知らせ -
地図アラート
↓この場所の近辺での新しいテニスオフが登録されたときにメールでお知らせ
子供服 女の子 秋冬 長袖 トップス 2点セット ウール混 ニットベスト カーディガン ケーブル編み かわいい おしゃれ カジュアル 普段使い 幼稚園 通園 3-8歳 100-140cm
LiLishop6
4500円
string{}.to_json()```/app/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/core_ext/object/json.rb:80:in `to_json'````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````The final output will be a single JSON array containing the parsed and filtered information. Due to the constraints, if no valid information can be extracted, an empty JSON array `[]` should be returned. The previous steps indicate that after applying all the rules, no product specifications remain. Therefore, the output should be an empty JSON array.```json[]```. This ensures compliance with the